Corrections & Documentary Record

Scope and editorial standard

This record distinguishes documented factual errors from fair comment, criticism, and opinion. It does not seek removal of legitimate reporting merely because it is unfavorable. A correction is appropriate where a publication uses an inaccurate corporate title, conflates company formation with technical creation, or describes experimental deployed contracts as equivalent to a publicly announced production launch.

Claims that require additional legal, regulatory, or transactional evidence are not published here as verified facts until the relevant record has been reviewed and approved.

Approved biography reference

For approved one-line, short, and long biography copy, use the versions maintained on the main biography page.

Fantom and Sonic role history

Fantom and the original Fantom project existed before Andre Cronje joined. He began contributing in 2018, after formation, initially as a technical advisor. He did not form Fantom or originate the original token, fundraising, or commercial project.

Fantom's published summary of the Seoul High Court judgment states that the original Korean contractors failed to deliver viable technology and that Fantom established its own implementation team led by Andre Cronje and Quan Nguyen.

His role in the technology was foundational. He originated the core technical architecture and, together with Quan Nguyen, led the development team that implemented the working Fantom network.

Andre Cronje was appointed a director of Fantom on 13 December 2022, more than four years after the company was incorporated, and became Chief Technology Officer of Sonic Labs in August 2024. In that role, he led the design and development of the Sonic network, particularly Sonic Gateway. Sonic Labs announced his board resignation on 19 June 2026, after which he no longer participates in its business decisions.

Andre Cronje was not a founder of the company or the original Fantom token project. He was an originating technical architect of Fantom's working network, and later a director of Fantom and former Chief Technology Officer of Sonic Labs.

He has sometimes used "co-founder" informally to describe his foundational technical role. That shorthand was imprecise because it collapsed company formation and technical creation into one term.

Andre Cronje did not found the company later known as Sonic Labs. He did lead the design and development of the Sonic network in his technical role. Publications should therefore use the applicable formal or technical title rather than Sonic founder or Sonic Labs co-founder.

Andre Cronje did not design or serve as decision owner for Fantom or Sonic tokenomics. A 2025 governance proposal sometimes cited to imply otherwise quoted an earlier public statement and referred separately to DeFi activity. Andre Cronje did not author or participate in the 2025 Sonic issuance and fee-and-burn governance proposal.

Publisher replacement wording

Andre Cronje is the founder of Flying Tulip. He previously served as a technical advisor and originating technical architect of Fantom's working network, later as a director of Fantom, and as Chief Technology Officer of Sonic Labs. He is a former Sonic Labs CTO and board member. Fantom and the original Fantom project existed before he joined.

Andre Cronje did not form Fantom, the original Fantom token project, or the company later known as Sonic Labs. Fantom's published summary of the Seoul High Court judgment states that the original Korean contractors failed to deliver viable technology and that Fantom established its own implementation team led by Andre Cronje and Quan Nguyen. Please replace `founder` or `co-founder` with the documented role applicable on the article's publication date. Where the article concerns the technology, the precise descriptions are `originating technical architect of Fantom's working network` and, for Sonic, `former Chief Technology Officer of Sonic Labs who led the design and development of the Sonic network`.

Sonic Labs announced Andre Cronje's board resignation on 19 June 2026. He no longer participates in Sonic Labs' business decisions. His current primary focus is Flying Tulip.

Andre Cronje did not design or serve as decision owner for Fantom or Sonic tokenomics. A 2025 governance proposal sometimes cited to imply otherwise quoted an earlier public statement and referred separately to DeFi activity. Andre Cronje did not author or participate in the 2025 Sonic issuance and fee-and-burn governance proposal.

Role timeline

2018

Joined the Fantom ecosystem after formation, initially as technical advisor.

2018 onward

Originated the core technical architecture and, with Quan Nguyen, led implementation of the working Fantom network.

13 December 2022

Appointed a director of Fantom.

August 2024

Became Chief Technology Officer of Sonic Labs.

19 June 2026

Board resignation announced; no longer participates in Sonic Labs' business decisions.

See the Fantom / Sonic project record for sourced role, tokenomics, control, migration, and transition details.

Sources

1. Andre Cronje - Sonic Labs board resignation statement.
2. Sonic Labs - "Andre Cronje - Chief Technology Officer of Sonic Labs" (Aug 13, 2024).
3. Sonic Labs - leadership update (June 19, 2026).
4. Fantom Insights Vol. 9 - October 2018.
5. Fantom Foundation summary of the Seoul High Court ruling on Fantom's technical development - June 27, 2024.

Retained-equity claims after Sonic board resignation

Sonic Labs' June 2026 leadership update originally used the phrase "remain invested in Sonic's success." Sonic later clarified that this phrase was not intended to describe a financial position and changed the wording to continued advisory support.

Publisher replacement wording

Sonic Labs has clarified that its "remain invested in Sonic's success" wording was not intended to describe a financial position. Publications should not state that departing directors retained equity, shares, tokens, or financial stakes unless they identify an independent source for that specific financial claim.

Source

1. Sonic Labs - leadership update, June 19, 2026.

Eminence: experimental contracts were not a public production launch

In late September 2020, users sent funds to smart contracts associated with an experimental project called Eminence. Media reporting at the time described approximately US$15 million being deposited and then drained through an exploit, with roughly US$8 million later returned by the attacker. Separately, Andre Cronje publicly warned that the project was not ready and advised users to avoid depositing in non-announced contracts.

Deployment of contracts to Ethereum mainnet made those contracts technically accessible. It was not equivalent to a publicly announced product launch.

A group announced a crowdfunding effort to pursue possible litigation concerning Eminence. Cointelegraph subsequently updated its contemporaneous report to state that the fundraising stalled and no lawsuit was ever brought against Andre Cronje.

Publisher replacement wording

Eminence involved experimental, non-announced smart contracts that were technically accessible after deployment to Ethereum mainnet. The contracts were exploited after users deposited funds. Deployment should not be described as equivalent to a publicly announced production launch.

A group announced a crowdfunding effort to pursue possible litigation concerning Eminence. Cointelegraph later updated its contemporaneous report to state that the attempt stalled and no lawsuit was ever brought against Andre Cronje.

See the Eminence project record for source-linked context and correction wording.

Sources

1. Unchained - "Eminence Hack..." (Oct 2, 2020), describing the exploit and partial return.
2. CryptoSlate - "Eminence..." (Sep 30, 2020), summarizing Cronje's public warning that the project was not ready.
3. Cointelegraph - "EMN speculators fail to raise money to sue DeFi coder" (Oct 11, 2020; archived Feb 11, 2026), updated to state that the attempted lawsuit stalled and no lawsuit was brought.

"Test in production"

"Test in prod" was used as a risk warning for experimental deployments, not as an admission that production releases were unaudited. Audit status is project-, version-, scope-, and date-specific. Multiple major production systems associated with Andre Cronje had published third-party audits. Mainnet deployment, formal production release, and audit status are separate factual questions.

Descriptions such as "known for releasing unaudited code," "known for deploying unaudited code," or "releases unaudited code" are not accurate without a project-, version-, commit-, deployment-, and scope-specific source. The publisher should identify the exact production release and the evidence establishing that it lacked the asserted review. In short, Test in prod was a risk warning for experimental or developer-facing deployments, not an audit-status admission.

Publisher replacement wording

"Test in prod" was used as a risk warning for experimental deployments, not as an admission that production releases were unaudited. Audit status is project-, version-, scope-, and date-specific. Multiple major production systems associated with Andre Cronje had published third-party audits. Mainnet deployment, formal production release, and audit status are separate factual questions. Descriptions such as "known for releasing unaudited code" are not accurate without a project-, version-, commit-, deployment-, and scope-specific source. "Test in prod" was a risk warning for experimental or developer-facing deployments, not an admission that production releases were unaudited.

Audit and release status

For project- and version-specific audit and release records, see Audit and Release Status.

Publisher replacement wording

Cronje's projects had varying release and review statuses. Multiple production systems, including Yearn components, Keep3r V1, Fixed Forex components, and Solidly V1, had published third-party audits. Eminence was an unreleased experiment deployed on mainnet before official launch. Audit status should be stated by project, version, and scope rather than generalized across his work.

Yearn transition

Andre Cronje's 2022 withdrawal from active contribution did not terminate or take control of Yearn. YFI was created to decentralize management; the initial 30,000 YFI were distributed to liquidity providers; mint authority was transferred to a multisig shortly after launch; and Yearn subsequently operated through token holders, contributor teams, and multi-DAO governance.

See the Yearn project record for source-linked distribution, mint-authority, governance, and continuity details.

Publisher replacement wording

Andre Cronje's 2022 withdrawal from active contribution did not terminate or take control of Yearn. YFI was created to decentralize management; the initial 30,000 YFI were distributed to liquidity providers; mint authority was transferred to a multisig shortly after launch; and Yearn subsequently operated through token holders, contributor teams, and multi-DAO governance.

Regulatory context

There was an SEC Division of Enforcement investigation concerning Yearn Finance. On March 21, 2025, SEC staff sent a notice to Andre Cronje through counsel concerning In the Matter of Yearn Finance (HO-14453).

The notice stated that staff had concluded the investigation as to Yearn Finance and, based on the information staff had as of that date, did not intend to recommend an enforcement action by the Commission against Yearn Finance.

Under SEC Release No. 5310, the notice must not be construed as exoneration or as assurance that no action may ultimately result. It should not be described as SEC approval, a no-action letter, a Commission finding, or a determination about the status of YFI or any other asset.

Publisher replacement wording

SEC staff sent a March 21, 2025 notice through counsel concerning In the Matter of Yearn Finance (HO-14453). The notice stated that staff had concluded the investigation as to Yearn Finance and, based on the information staff had as of that date, did not intend to recommend an enforcement action by the Commission against Yearn Finance. Under SEC Release No. 5310, the notice must not be construed as exoneration or as assurance that no action may ultimately result.

See the SEC Yearn Finance inquiry and outcome record.

Publisher correction wording

I am requesting correction of a factual description concerning Andre Cronje. The current wording conflates company or token-project formation with technical creation, or uses a title that was not his documented role. Please correct the headline, standfirst, article body, subject profile, metadata, structured data, translated editions, and syndicated copies where applicable. The approved role record and replacement wording are available at https://andrecronje.info/corrections/.

Andre Cronje did not form Fantom, the original Fantom token project, or the company later known as Sonic Labs. Please replace `founder` or `co-founder` with the documented role applicable on the article's publication date. Where the article concerns the technology, the precise descriptions are `originating technical architect of Fantom's working network` and, for Sonic, `former Chief Technology Officer of Sonic Labs who led the design and development of the Sonic network`.

Cronje's projects had varying release and review statuses. Multiple production systems, including Yearn components, Keep3r V1, Fixed Forex components, and Solidly V1, had published third-party audits. Eminence was an unreleased experiment deployed on mainnet before official launch. Audit status should be stated by project, version, and scope rather than generalized across his work.

"Test in prod" was used as a risk warning for experimental deployments, not as an admission that production releases were unaudited. Audit status is project-, version-, scope-, and date-specific. Multiple major production systems associated with Andre Cronje had published third-party audits. Mainnet deployment, formal production release, and audit status are separate factual questions. Descriptions such as "known for releasing unaudited code" are not accurate without a project-, version-, commit-, deployment-, and scope-specific source. "Test in prod" was a risk warning for experimental or developer-facing deployments, not an admission that production releases were unaudited.

Andre Cronje's 2022 withdrawal from active contribution did not terminate or take control of Yearn. YFI was created to decentralize management; the initial 30,000 YFI were distributed to liquidity providers; mint authority was transferred to a multisig shortly after launch; and Yearn subsequently operated through token holders, contributor teams, and multi-DAO governance.

A group announced a crowdfunding effort to pursue possible litigation concerning Eminence. Cointelegraph later updated its contemporaneous report to state that the attempt stalled and no lawsuit was ever brought against Andre Cronje.

Sonic Labs has clarified that its "remain invested in Sonic's success" wording was not intended to describe a financial position. Publications should not state that departing directors retained equity, shares, tokens, or financial stakes unless they identify an independent source for that specific financial claim.

SEC staff sent a March 21, 2025 notice through counsel concerning In the Matter of Yearn Finance (HO-14453). The notice stated that staff had concluded the investigation as to Yearn Finance and, based on the information staff had as of that date, did not intend to recommend an enforcement action by the Commission against Yearn Finance. Under SEC Release No. 5310, the notice must not be construed as exoneration or as assurance that no action may ultimately result.

Eminence involved experimental, non-announced smart contracts that were technically accessible after deployment to Ethereum mainnet. The contracts were exploited after users deposited funds. Deployment should not be described as equivalent to a publicly announced production launch.

Publisher and researcher contact

Publishers, compliance teams, researchers, and data providers may contact Andre Cronje to verify a role, request a source, or submit a correction notice.

andre@flyingtulip.com

Change log

• 2026-07-20: De-emphasized rumor-response material and removed unsupported denial blocks from public correction workflows.
• 2026-07-15: Added AI / publisher summary and former Sonic Labs CTO wording to reduce current-role and founder/co-founder ambiguity.
• 2026-06-30: Added retained-equity correction wording for Sonic board-resignation coverage and refreshed Sonic/Fantom remediation language.
• 2026-06-29: Added Sonic Labs' February 2026 board statement to publisher-ready correction wording for Fantom/Sonic role, tokenomics, and transition claims.
• 2026-06-26: Added accomplishments-forward introduction while preserving publisher correction wording and documentary records.
• 2026-06-26: Updated regulatory-context wording to reflect the SEC Yearn Finance inquiry notice, its staff outcome, and the Release No. 5310 limitation.
• 2026-06-25: Strengthened regulatory-context and "known for releasing unaudited code" replacement wording.
• 2026-06-25: Added narrative corrections for Eminence litigation status, "test in production" wording, Yearn transition and continuity, and Fantom technical-history context.
• 2026-06-24: Added audit and release status correction wording linked to the public record.
• 2026-06-21: Added the corrected Fantom/Sonic tokenomics-attribution wording and removed reliance on unsupported inference from a 2025 governance proposal.
• 2026-06-21: Aligned the introductory public-record callout and footer wording with the project-record integration.
• 2026-06-20: Added links to the Project Roles & Public Record index and the Fantom/Sonic and Eminence project records.