IMF

🟢IMF V4 is LIVE Launch coins with their own ENS for FREE on Ethereum. Here's how to launch a token in 30 seconds 👇

"whats next for the IMF?" What if...? Ahaha. Just kidding. Unless...

Three vaults/protocol entities still require manual settlement coordination before distributions can be completed. These are: 0x25D385fCab771e36a826BBFB47e2Ddaa2f19D449 0x786977528B0265C5C5Bc9544ac56C863c03e34D1 0x2E87d6bfA3F2A932e0c70A32607c0B839404984D If you are the owners of these vaults, please contact: gm@imf.bz Please include: - wallet address - relevant transaction hashes - supporting information relating to the lender position Further instructions will follow after review.

LENDER RECOVERY DISTRIBUTION UPDATE As part of the coordinated recovery effort following the Incident, Recovery Contributions have now been distributed to 8 eligible lender addresses. Distribution transaction: etherscan.io/tx/0x147e02c9b… Distributions were made in USDC on Ethereum

RECOVERY DISTRIBUTION METHODOLOGY The coordinated recovery distribution was calculated using a methodology based on direct Incident-related economic harm within IMF-serviced markets active at the time of the Incident. 1. What snapshot was used? All calculations used the final clean on-chain state immediately before the Incident. Snapshot block: 25030091 Incident block: 25030092 This snapshot was used for borrower positions, lender exposure, collateral pricing and market state calculations. 2. What price was used? Collateral values were calculated using on-chain oracle prices sampled at the snapshot block. This avoided using distorted Incident pricing or later market pricing. 3. What asset was distributed? All Recovery Contributions were distributed in USDC on Ethereum Mainnet. Affected Parties received USDC-equivalent value rather than replacement collateral assets. 4. Which users were included? The coordinated recovery framework applied to eligible Affected Parties within IMF-serviced markets active at the time of the Incident. 5. How were borrower recoveries calculated? Borrower recoveries were calculated using direct Incident-related economic harm. In practical terms, this was based on: Eligible seized collateral value at snapshot pricing minus outstanding liabilities at the snapshot state. 7. Were recipient wallets reviewed? Yes. Recipient wallets were reviewed for sanctions and prohibited-wallet concerns prior to distribution. 8. How can users verify the distribution? Recovery wallet: 0x55d6A17dC894BD21628eb5e36c8e8dFf5B618f47 Distribution transaction: etherscan.io/tx/0x19fa00876… IMF has retained allocation records, transaction hashes and reconciliation records relating to the coordinated recovery distribution.

BORROWER RECOVERY DISTRIBUTION COMPLETE The coordinated recovery distribution has now been completed for Affected Parties. Distribution transaction: etherscan.io/tx/0x19fa00876… The distribution was made in USDC on Ethereum Mainnet. Further reconciliation details are below 👇

Recovery distributions will be administered from the following address: 0x55d6A17dC894BD21628eb5e36c8e8dFf5B618f47 Users are encouraged to monitor this wallet for outgoing recovery transactions. A separate announcement will follow once distributions have been completed. etherscan.io/address/0x55d6…

UPDATE The second tranche recovery payment of 200,000 USDC has now been received. The team is currently finalising the recovery distribution process. Distribution is expected to begin within the next few hours. Further details and transaction updates will follow shortly.

For clarity, the coordinated recovery process is intended for affected lenders and borrowers within IMF-serviced 62.5% LLTV markets active at the time of the Incident. As previously communicated, IMF had deprecated and ceased servicing 77% LLTV markets prior to the Incident, and those markets are not included within the coordinated recovery framework. Further details regarding eligibility and distribution methodology will follow. 3/3 x.com/IMFCrypto/stat…

Additional recovery funds are expected to arrive in a second tranche payment on Monday, May 18th. The recovery wallet receiving funds is: 0x55d6A17dC894BD21628eb5e36c8e8dFf5B618f47 Further updates regarding the recovery and distribution process will follow in due course. 2/3

FULL RECOVERY AMOUNT SECURED Following the incident, IMF and DIA collaborated closely to coordinate recovery efforts for affected funds and users. DIA has been a reliable partner, acting efficiently and quickly to assist, and the Parties have focused on a successful and prompt recovery process. 1/3

All IMF V4 tokens earn creator fees. The test.imfx.eth deployer has already earned 0.8 ETH in creator fees. Launch coins with their own ENS for FREE on Ethereum: app.imf.bz/x

"What's the CA?" Contract Addresses are 42 characters long. IMF V4 tokens have a dedicated ENS subdomain. Launch a token now for FREE on Ethereum and secure your ENS now: app.imf.bz/x

@gami_vc MemeFi United

Testcoin $TEST CA: test.imfx.eth All fees to memefiunited.eth

For more info, read our docs: docs.imf.bz Launch your token now: app.imf.bz/x

Every IMF V4 token also comes with it's own @ensdomains. On deployment, every ticker belongs to a unique subdomain under imfx.eth No need to remember CAs with 42 characters.

🟢IMF V4 is LIVE Launch coins with their own ENS for FREE on Ethereum. Here's how to launch a token in 30 seconds 👇

@0xPajke They need to mog 50% harder using the IMF. Few.

How is MOG coin not pumping rn