Users Who Purchased DEI
During the May 5 Incident
Last updated
During the May 5 Incident
Last updated
As the nature of the exploit was such that it prevented us from divulging specific details, to deter potential copycat attempts. We are aware that our communication during this period may have appeared unclear to some, despite our repeated advisories not to interact with the contracts. Therefore, we consistently conveyed our intent to compensate the cost basis for all affected users, barring a few exceptions.
Those who capitalized on the incident, those who exploited the flaws in the DEI contract, and those demonstrating malicious intent will be exempted from this reimbursement scheme. While we choose not to disclose the complete specifics of our investigative process, we thank you for your understanding and cooperation in this matter.
The DEUS team calculated your cost basis, subtracted any profits made, and will grant one bDEI for each USD of the adjusted cost basis. A more comprehensive explanation of how bDEI operates and how it can be utilized to offset debt is available in a specific section of our Gitbook. We highly recommend that you read it for a thorough understanding. bonded DEI (bDEI) / SYMM / DEUSmigration /
The option to retain your bDEI in anticipation of a potential recovery of additional USDC. Alternatively, users can migrate their holdings to SYMM or DEUS, thereby making it liquid and sellable but also eligible to earn protocol profits in the future. More details on this process are elaborated upon in a subsequent section of the Gitbook. SYMM / DEUSmigration
An explanation to why bDEI should be migrated and cannot earn protocol profits as bDEI is detailed here bonded DEI (bDEI)
The links to the announcements and detailed procedures can be found below:
[Announcement Links] [Gitbook Section Links]
Thank you for your continued trust and support in DEUS as we strive to rectify this situation and safeguard our community's interests.