Public record
Eminence: Development Status, Exploit, and Returned Funds
Summary
Eminence was an unreleased experimental system.
Its pre-production contracts were deployed on Ethereum mainnet, which made direct third-party interaction technically possible before an official product release. Contemporary reporting described approximately US$15 million being extracted and approximately US$8 million being returned, followed by a partial-refund process.
The correct description is pre-production contracts deployed on mainnet. Eminence should not be described as a testnet project, but mainnet deployment was also not equivalent to an announced production launch.
Facts at a glance
| Question | Public record |
|---|---|
| Had Eminence been officially released? | Contemporary reporting described it as unreleased and exploited before going live. |
| Where were the contracts deployed? | Ethereum mainnet. |
| Could third parties interact with them? | Yes, because the contracts were publicly callable on mainnet. |
| What was reported lost and returned? | Approximately US$15 million extracted and approximately US$8 million returned. |
| Was compensation reported? | Yes. Contemporary reporting documents a partial-refund process. |
| Does this page state that no lawsuit was ever filed? | No. It records only what the identified public sources establish. |
Verified public record
Development and release status
Contemporary reporting described Eminence as unreleased and as having been exploited before going live.
There was no finished, announced production release in the record reviewed for this page. At the same time, the contracts were deployed to Ethereum mainnet and were technically accessible.
The accurate distinction is:
Eminence involved pre-production smart contracts deployed on Ethereum mainnet. Technical accessibility was not the same as an announced production launch.
Exploit and returned funds
Contemporary reporting described:
- Approximately US$15 million being extracted.
- Approximately US$8 million later being returned.
- A subsequent process to distribute returned funds to affected participants.
A transaction-by-transaction reconciliation should be added before publishing more precise statements about total eligible claims, distributions, unclaimed funds, or every wallet involved.
Litigation-related reporting
A contemporaneous report located for this record described a group raising funds to pursue possible litigation.
That report did not itself identify a filed complaint, court, or case number. This page does not make a categorical statement about whether any proceeding was filed later. A definitive statement should follow a counsel-led docket search identifying jurisdictions, databases, names, entities, and limitations.
Responsibility I accept
- Deploying publicly callable pre-production contracts on mainnet created a foreseeable discovery and interaction risk.
- Public discussion of unfinished work can influence behavior even without a formal launch.
- The absence of an official interface or sale does not erase the losses suffered by third parties.
- The deployment and communication process should have included stronger safeguards.
What the public record does not establish
The sources reviewed for this page do not establish:
- That Eminence was deployed on a testnet.
- That every returned dollar was distributed.
- My complete wallet-level profit or loss from the incident.
- A definitive global finding that no lawsuit was ever filed.
- That a proposed lawsuit or its fundraiser was fraudulent.
Sources
- EMN-01: Andre Cronje Diehards Take 'Test in Prod' Over The Edge With $15M Hack — The Defiant — 2020-09-29. Source tier C;
contemporaneous_reporting. - EMN-02: Hackers Drain $15 Million From Unreleased Yearn Finance Project — Decrypt — 2020-09-29. Source tier C;
contemporaneous_reporting. - EMN-03: Eminence Refund — Do or DAI — Rekt — 2020-10-01. Source tier C;
contemporaneous_reporting. - EMN-04: Group raising funds to sue Andre Cronje over EMN hack — Cointelegraph via Investing.com — 2020-10-11. Source tier C;
contemporaneous_reporting.
Change log
- 2026-06-20: Initial publication.