Muon Weekly Community Recap 💻 Pion token contract audit is scheduled for the 10th of July 👮 Presale Verifier bot has been added to Discord. Get your Presaler badge now 🤝 @ThenaFi_ partners with @pendle_fi

IMPORTANT: Multichain situation DOES NOT impact DEUS users or any other assets within our larger ecosystem.

📣 PION Token Audit Scheduled for July 10th The upcoming PION token audit is scheduled for the 10th of July. After the audit, we will implement all token features on ALICE.

Epoch 1 bribes for $FVM ✅

Plenty of opportunities to earn some $DEUS rewards this week across multiple chains 🔥 Get your votes in before the Epoch flip! 350 DEUS rewards for the taking on @VelocimeterDEX

t.co

Hello everyone, As we approach the final phase of the reimbursement process, we are now 99% certain we've captured all bugs and have begun collecting the final data to calculate the actual reimbursement values for our short-term reimbursement plan. IMPORTANT NOTE - this reimbursement plan is ONLY for users that held DEI or LPs with DEI BEFORE the incident. Our Short-Term reimbursement approach primarily targets users that held DEI before the incident. However, we are also mindful of the users who purchased DEI after the incident; they will be considered in our long-term reimbursement plan. Now, we'd like to explain in detail how we calculate the reimbursableAmount for affected DEI users who had DEI before the incident: Starting with the total DEI in wallets and held in LPs together with USDC before the incident, subtract USDC that was removed via LPremovals and subtract DEI sold into LPs or burnt via redemption contracts. Note that transferred or bridged DEI will not be subtracted from your balance. The final value, referred to as the 'reimbursableAmount,' represents your final balance. userDEIbefore plus userUSDCbefore minus userUSDCamountWithdrawn minus userDEISold = reimburseableAmount For your options, there are two plans. First, a short-term reimbursement plan paid out in USDC that carries a haircut USDC amount. Secondly, a long-term reimbursement plan is paid out in a newly launched DEI (expected in Q4), which carries a haircut DEI amount. You can either get USDC now or wait until Q4 and receive a newly launched DEI later. Since DEI was only 90% backed, taking USDC now would mean a higher haircut. Therefore the Haircut in USDC is more significant than in (Q4 relaunched) DEI. To illustrate: Suppose you have a 10,000 reimbursableAmount, with a hypothetical haircutUSDCAmount value of 0.65. You decide to take 40% in USDC now, redeeming 4000 of your reimbursable amount, which leaves you with 6000. You would then receive 2600 USDC now (4000 * 0.65). Please note that the 65% haircut for USDC is hypothetical. The actual haircut values will be released, likely by the end of this week, alongside a new website where you can check your values. To simplify the accounting for the long-term reimbursement plan, we will provide you with one bDEI for each $1 amount that you couldn't claim because of the given haircut percentage. Using the previous example, you would receive 2600 USDC now and 1400 in bDEI, and you would keep 6000 as reimburseableAmount for claiming later (the remaining amount of your initial 10,000). These bDEI will be redeemable for other currencies as soon as the protocol can repay the outstanding amount. We are committed to making this process as fair, transparent, and convenient as possible. We understand this is a challenging time for all Deus community members, and we appreciate your understanding and patience. Your trust in Deus remains our top priority. We promise to keep you updated throughout the process and are grateful for your continued support. Please don't hesitate to contact us with any questions or concerns. Join the DEUS Discord server for the main discussion area, thanks! 🫡

discord.gg

Dear Community Members, We have successfully fixed all bug report applications. The snapshot data should now be 100% complete and accurate as of this moment. We will keep a 72-hour window open for any last-minute claims or reports from your end. Once this period concludes, we will consider the data to be final. We advise everyone to do a final check on his values using this page:

app.dei.finance

🙏 However, we have already started preparations for determining the final reimbursement values. We aim to provide a detailed breakdown of the exact reimbursement values for everyone around mid to end of next week, staying on course with our latest updated timeline. Then we would: 1️⃣ propose a reimbursement plan, 2️⃣ give a grace period for discussing the reimbursement approach, 3️⃣ start preparing contracts to claim USDC, 4️⃣ let everyone affected claim their USDC Stay tuned for more updates next week

We are releasing the full snapshot data. This snapshot includes a total of 323 variables and 5479 wallets. 📊 To view all raw variables, follow this link: 🔗

pastebin.com

We have deployed a quick n dirty API for everyone to check the data specific to his wallet. Paste wallet address in the provided space here: 🔗

info.deus.finance

Our team is also working to prepare a webpage for users to directly connect their wallet and get the data in human readable format, which we anticipate will be ready within 24-48 hours. 🕒 To ensure accuracy and transparency, we have established a Typeform for anyone to report any irregularities in his snapshotted balances: 🔗

7eoku1wmhjg.typeform.com

Everyone's assistance is invaluable in helping us ensure the snapshot data is sound and 100% accurate. Please note, however, that due to file size limits of 526kb and 3000 kb on Pastebin and pastes.io, respectively, we were unable to upload the full raw file there. We will upload the file on our webservers so you can download it if you are interested in having the full raw data. Download link will come shortly To help everyone understand the data better, here is a quick explainer about the variables and what they mean: LP balance Beets(USDC/DEI) before: User's LP balance before the incident LP balance Beets(USDC/DEI) now: User's LP balance right now LP Beets(USDC/DEI) token 0 before: USDC amount of the user's LP tokens before the incident LP Beets(USDC/DEI) token 1 before: DEI amount of user's LP tokens before the incident Redeem DEI Redeem DEUS Redeem USDC x y z User has redeemed x DEI and collected y DEUS and z USDC in return Buy DEI Buy USDC Buy USDT x y z User has bought x DEI in return of y USDC and z USDT Sell DEI Sell USDC Sell USDT x y z User has sold x DEI in return of y USDC and z USDT Arbitrage x: User uses x token for arbitrage (transaction or swaps have gone through one or more of DEI LP pair). For example, if a user gave 100 units of x and got back 102 units in a transaction, the value of this variable would be 2.

Dear Community, Update on the DEI balance reinstatement As per our previous communication and elaborated in our GitBook, the DEUS team is preparing snapshots to reinstate all DEI balances. The primary objective has been to restore all balances to the state before the incident considering all actions taken during the incident until all contracts were put on hold. Final progress: Subgraph to track DEI transfers across different chains: 90% complete. Subgraph specifically for DEI LPs: Completed. Identification of all DEI LPs and their quantities: Completed. Composition of a complex script to analyze transfers from the subgraphs: 90% complete. Data Verification and Resolution of Any Discovered Bugs: We are about to finalize the snapshot data and aim to release it by the end of next week. Then, a public verification period of 1-2 weeks will be followed, where every user can validate their balances and report any irregularities through a dedicated form. The public verification process will assist us in identifying and addressing potential issues or bugs. We will propose a restoration plan as soon as we have concrete data. Timeline: 20.05 - 02.06: Manual restoration of about 200 transactions that the snapshot tools could not track due to their unusual or complex structure. 03.06-04.06: Final internal checks on data to ensure data integrity before public release. 04.06 - 11th or 18th of June: (Depending on user feedback) we will make snapshot adjustments, fix bugs in the snapshot software and validate claims of irregularities. 11-30th of June (depending on severity of irregularities in released data and user feedback) Short-term reimbursement plan, we will release the final snapshot data, propose a short-term reimbursement plan, and set up a contract to claim your USDC. Afterwards we will work on a Long-term reimbursement. A more comprehensive recovery plan will be developed for those interested in participating in the long-term success of DEUS, including the potential relaunch and reimbursement from future profits. We empathize with those in urgent need of funds, but we ask for your understanding as we strive for absolute accuracy in our data. Any premature or partially executed reimbursement could lead to discrepancies and disputes, negatively affecting others affected by the incident and potential irregularities in their data. Therefore, we must be 100% certain about the data before proceeding with any form of reimbursement. We appreciate your patience and support during this process, and we are committed to ensuring a fair and thorough resolution. On another note, we encourage those interested in DEUS v3 updates, the new upcoming frontends, and anything related to Cloverfield development to join the Cloverfield Discord. During this period of DEI reimbursement, we will be sharing relevant information exclusively through this platform.

discord.gg

Best regards, Lafayette

Dear community members, We prepared a weekly status update on the work currently in progress to rectify the recent issues with DEI balances. As conveyed in our previous announcement and detailed in our GitBook, the DEUS development team is preparing the necessary snapshots. These snapshots will serve as the foundation for accurate reimbursement of DEI holders; only with accurate accounting can we reimburse everyone, as the situation was complicated by the actions of valuable whitehats, who helped to pause all contracts by using the flaw in the burnFrom function to burn all users balances. Our priority continues to be restoring all balances to their state before the attack and until all contracts were paused. The frantic activities of numerous users, who moved their DEI during this chaotic period, have made this snapshot process complex and time-consuming. The snapshots also needs to cover a variety of actions, such as buying, transferring, and selling DEI, as well as removing LP. Here is the current progress on the tasks related to snapshotting: Subgraph to Track DEI Transfers Across Different Chains: 75% completion. Subgraph Specifically for DEI LPs: also at 75% completion. Identification of All DEI LPs, Including Smaller Quantities: current status at 70%. Composition of an Intricate Script to Analyze Transfers from the Subgraphs: now at 60%. Data Verification and Resolution of Any Discovered Bugs: We have yet to initiate this phase, current status is 0%. We understand the need for transparency and clarity we will persist in keeping you informed with updates as we progress.

We released new sections in the Deus GitBook, dedicated to providing an in-depth post-mortem analysis of the recent event. here:

docs.deus.finance

Transparency is vital to resilience and growth, and we are committed to providing as much clarity and information as possible. Sections Now Live: Initial Report of What Happened: We've documented the events as they unfolded, giving you a clear timeline and an initial understanding of the situation. Summary: This section offers a condensed and comprehensive overview of the incident, making it easier to grasp the overall picture. (will be updated with all new information surrounding the recovery plan and steps forward) Detailed Attack Rundown: For those seeking more specifics, we provide a step-by-step examination of the attack. This detailed account aims to shed light on the complex dynamics involved in the unfortunate event. Sections Under Development: Reimbursement & Recovery Plan: We're finalizing the details of our plan to ensure all affected parties are adequately compensated and to outline our recovery strategy moving forward. Cause of the Exploit: We're preparing a thorough analysis explaining the root cause of the exploit, including a deep dive into the purpose and reasoning for implementation of the burnFrom function. Steps forward: In this section, we will share our plans for restructuring and improving our protocol processes, including ideas about derisking the protocol from DEI. We greatly appreciate your support and patience as we work through the recovery process. Please stay tuned for updates on the release of these upcoming sections.

Subject: DEI Incident Update - 08.05.2023 Dear DEUS Community, As of today, 08.05.2023, we have made significant progress in recovering the affected funds. Thanks to the joint efforts of the DEUS team, Chain analysis, and reputable whitehats in the space, we have managed to retrieve the following: 1️⃣ 2023 ETH from the initial attacker on Arbitrum Source:

twitter.com

2️⃣ 702,480.99 USDC from @adamb83024264, @paladin_marco, and @pcaversaccio on Arbitrum Source:

twitter.com

3️⃣ 1,070,127 DAI from the MEV bot that blocked and front-ran the initial attack on BSC Source:

twitter.com

Total recovery figure estimates at this moment The total recovered funds now amount to nearly 5.5 million out of the 7 million initially affected as per media coverage. That puts the total recovery rate at approximately 70%-80%, including ALL LP deposits (also including their USDC/USDT parts). Addressed to those who tried to profit but are now stuck: We also want to directly address those who interacted with DEI contracts during the attack despite the team's warning. As the nature of this exploit allowed funds to be moved out of every wallet, our only logical approach was to stop the attack by pausing ALL contracts. The team repeatedly asked the community to refrain from interacting further with DEI contracts throughout the night of 5th May, therefore there is currently nothing we can do to roll that transactions back until the full snapshot and reimbursement program is finalized. At this point we ask you as all other dei holders to remain patient until the full reimbursement plan is laid out. To anyone who was able to profit from the situation Additionally, due to the nature of this attack, it opened arbitrage opportunities for essentially everyone. These funds have to be lawfully returned to the LP owners. We will contact all those profiting from market operations during the exploit and offer them a similar white hat bounty for their efforts as the MEV bot and the initial attacker on Arbitrum received. We ask these market participants, to reach out to the team onchain or via email to info@deus.finance Important Note to manage expectations: The definite backing number is dependent on arbitrage profits and users' actions, and the exact figure can only be given once all snapshots have been taken, please be aware that the entire reimbursement (which includes people still stuck in LPs, bridges, or users who still hold DEI on ANY chain) process may take some days, up to a few weeks. However, we expect that during the time it takes to prepare the snapshots and reimbursement contracts, additional Market Participants and whitehats will be returning funds, increasing the total to be reimbursed percentage even higher. We appreciate the continued support and patience of the community as we work diligently to resolve this situation. We will keep everyone informed here and on twitter of further updates and developments. Sincerely, The DEUS Team

Update 07/05/2023 regarding the DEI incident. We will continue to give regular updates on the situation, and information will be shared as it's examined, but as this exploit created a window where everyone could take action to profit from this attack, rolling everything back takes a lot of time. We started identifying the factual backing of DEI across all chains and communicating successfully with Whitehats to return a good chunk. BSC MEV bot returned 1M:

bscscan.com

Paladin Security returned 100k:

arbiscan.io

Adamb returned 600k + (3263) DEUS:

arbiscan.io

in addition to the backing, you can see live on

app.dei.finance

If we rolled all of this into the DEI backing to ensure everyone's redemption equally across all chains, the current DEI backing would be 75% (please understand that the actual backing can only be defined by understanding everyone's balances and calculating the amount of DEI that should be getting returned; as we are still rolling everything up, these values can change; this should give everyone a first estimate, we will continue to analyze onchain data and update you on the progress. current action plan 1️⃣ Prepare snapshots to reinstate DEI balances of Users that got their LPs drained to let them reclaim their DEI balance. 2️⃣ Create a snapshot of all currently "stuck" DEI (DEI that was bought during the incident and is stuck on bridges or other chains) and prepare a snapshot for them to return their cost basis + bounty. 3️⃣ Create a redemption contract for everyone. 4️⃣ Continue communication with Whitehats or law enforcement to discuss returning funds to increase backing further. Please remain patient as we prepare these next necessary steps, thanks 🙏

Update on DEI tokens security breach Yesterday: In response to the security breach, all contracts were paused, and DEI tokens on chains were burnt to prevent further damage. Today: We are currently in the process of comprehending the actual backing of DEI tokens. To achieve this, snapshots of all DEI balances are taken before the tokens are burnt. After evaluating all balances, we will formulate a comprehensive recovery and redemption plan. Important Note: For users who attempted to arbitrage after the hack and are now stuck, there will be an evaluation, and they may be allowed to reverse these transactions as soon as possible. This action would involve burning the outstanding DEI and increasing the backing of all other users. Users are advised to remain patient and not interact with current DEI contracts until a concrete redemption plan is available. The current DEUS v3 system is (and was in the past) isolated from DEI, meaning it is totally unaffected by the events.

Morning sirs, please make sure you have read this annoucement

t.me

and when the full situation is assessed we'll be able to give you a full explanation of what has happened and what is going to happen going forward. At the moment, you are most likely best to sit where you are if you have DEI or LPs containing DEI, on any chain. This is not official advice but is what I would suggest taking all factors into account. There will be a plan of action going forward and of course this will be announced when possible but can only ask for your patience while the team do what needs to be done at the moment, thank you 🙏