{ "schema_version": "1.0.0", "last_reviewed": "2026-06-20", "canonical": "https://andrecronje.info/public-record/", "subject": { "type": "Person", "name": "Andre Cronje", "url": "https://andrecronje.info/" }, "editorial_standard": "The record distinguishes creation, formal authority, economic interest, custody/control, transition, and continuity. Where the public record is incomplete, it states that limitation rather than converting it into a categorical denial.", "projects": [ { "project_id": "yearn", "name": "iEarn / yEarn / Yearn Finance", "canonical_path": "/public-record/yearn/", "relationship_type": "creator and initial developer", "period": "2019/2020 onward; active involvement changed over time", "safe_public_summary": "Andre Cronje created the system that became Yearn Finance. Yearn's own documentation states that the initial 30,000 YFI were distributed to liquidity providers and that Andre initially controlled the token's minting function before transferring it to a multisig shortly after emissions began. Yearn later adopted multi-DAO governance and continued operating independently. This record concerns the initial distribution and control transition; it does not claim that Andre never later acquired, held, sold, or received YFI.", "claims": [ { "claim_id": "YFI-C01", "claim": "Andre Cronje is publicly identified as Yearn's creator and initial developer.", "status": "supported_public_reporting", "evidence_ids": [ "YFI-03" ], "qualification": null }, { "claim_id": "YFI-C02", "claim": "Yearn's current documentation states that the initial 30,000 YFI were distributed to liquidity providers.", "status": "verified_public_record", "evidence_ids": [ "YFI-01" ], "qualification": null }, { "claim_id": "YFI-C03", "claim": "No separate founder allocation is identified in the documented initial 30,000-token distribution.", "status": "verified_public_record", "evidence_ids": [ "YFI-01" ], "qualification": "This addresses the initial distribution only; it does not establish Andre's later purchases, compensation, grants, holdings, or sales." }, { "claim_id": "YFI-C04", "claim": "Andre initially held sole control of the YFI minting function and transferred that control to a multisig shortly after emissions began.", "status": "verified_public_record", "evidence_ids": [ "YFI-01" ], "qualification": null }, { "claim_id": "YFI-C05", "claim": "Yearn later transitioned to a multi-DAO governance structure involving YFI holders, yTeams, and a multisig.", "status": "verified_public_record", "evidence_ids": [ "YFI-02" ], "qualification": null }, { "claim_id": "YFI-C06", "claim": "Yearn continued to operate after Andre's active role changed and after his March 2022 departure announcement.", "status": "supported_public_reporting", "evidence_ids": [ "YFI-02", "YFI-03", "FTM-03" ], "qualification": null }, { "claim_id": "YFI-C07", "claim": "Andre's complete historical YFI holdings, sales, grants, and compensation are not established by the public sources in this ledger.", "status": "not_publicly_established", "evidence_ids": [], "qualification": null } ], "accountability": [ "Andre created the original system and initially controlled the YFI minting function.", "The initial transfer from founder control to collective control was a deliberate governance transition, not evidence that founder control never existed.", "Public statements and departure decisions could materially affect market expectations even after formal control had decentralized." ], "last_reviewed": "2026-06-20" }, { "project_id": "keep3r", "name": "Keep3r Network", "canonical_path": "/public-record/keep3r/", "relationship_type": "creator and initial developer", "period": "2020 onward; community and related repositories continued", "safe_public_summary": "Andre Cronje created Keep3r as a decentralized keeper and job network. Contemporary launch coverage quoted his announcement that there was no raise, sale, or initial distribution, that supply began at zero, and that participants earned KP3R by registering and performing work. Public repositories document the protocol and related work such as Fixed Forex. The public launch record does not establish Andre's later KP3R holdings, sales, compensation, or every historical admin right.", "claims": [ { "claim_id": "KPR-C01", "claim": "Andre created and publicly launched Keep3r as a decentralized network connecting jobs with external keepers.", "status": "supported_public_reporting", "evidence_ids": [ "KPR-01", "KPR-02" ], "qualification": null }, { "claim_id": "KPR-C02", "claim": "Contemporaneous launch reporting quoted Andre saying there was no raise, no sale, no initial distribution, and supply started at zero.", "status": "supported_public_reporting", "evidence_ids": [ "KPR-02" ], "qualification": null }, { "claim_id": "KPR-C03", "claim": "The quoted initial distribution mechanism required participants to register as keepers and perform work to earn KP3R.", "status": "supported_public_reporting", "evidence_ids": [ "KPR-02" ], "qualification": null }, { "claim_id": "KPR-C04", "claim": "The public launch was described as beta and included an express warning that audits and review did not eliminate bug risk.", "status": "supported_public_reporting", "evidence_ids": [ "KPR-02" ], "qualification": null }, { "claim_id": "KPR-C05", "claim": "Public repositories document Keep3r contracts, audits, migrations, and continuing community documentation.", "status": "verified_public_record", "evidence_ids": [ "KPR-01" ], "qualification": null }, { "claim_id": "KPR-C06", "claim": "Fixed Forex is publicly documented as related work within the Keep3r organization.", "status": "verified_public_record", "evidence_ids": [ "KPR-03" ], "qualification": null }, { "claim_id": "KPR-C07", "claim": "Andre's later KP3R holdings, sales, fees, compensation, and all historical admin rights are not established by the current public-source set.", "status": "not_publicly_established", "evidence_ids": [], "qualification": null } ], "accountability": [ "Andre designed and released the initial token and job-network mechanics.", "Calling a release 'beta' and warning of bugs does not remove responsibility for deployment choices or communications.", "Later decentralization or community maintenance should not be used to erase founder-period authority." ], "last_reviewed": "2026-06-20" }, { "project_id": "eminence", "name": "Eminence", "canonical_path": "/public-record/eminence/", "relationship_type": "developer of unreleased experimental system", "period": "September 2020", "safe_public_summary": "Eminence was an unreleased experimental system whose pre-production contracts were deployed on Ethereum mainnet. Contemporary reporting says third parties interacted with it before official launch, approximately $15 million was extracted, and approximately $8 million was returned, after which a partial-refund process was undertaken. Contemporary litigation coverage described fundraising to pursue a possible lawsuit. This ledger does not make a definitive 'no lawsuit was ever filed' claim until counsel completes and publishes an appropriate docket-search memorandum.", "claims": [ { "claim_id": "EMN-C01", "claim": "Eminence was publicly described contemporaneously as unreleased and as having been exploited before going live.", "status": "supported_public_reporting", "evidence_ids": [ "EMN-01", "EMN-02" ], "qualification": null }, { "claim_id": "EMN-C02", "claim": "The contracts were pre-production but deployed on Ethereum mainnet, making direct third-party interaction technically possible.", "status": "supported_public_reporting", "evidence_ids": [ "EMN-01", "EMN-02" ], "qualification": "Use 'pre-production contracts deployed on mainnet,' not 'testnet project.'" }, { "claim_id": "EMN-C03", "claim": "Contemporaneous sources reported approximately $15 million extracted and approximately $8 million returned.", "status": "supported_public_reporting", "evidence_ids": [ "EMN-01", "EMN-02" ], "qualification": null }, { "claim_id": "EMN-C04", "claim": "Contemporaneous reporting documents a refund or partial-compensation process using returned funds.", "status": "supported_public_reporting", "evidence_ids": [ "EMN-03" ], "qualification": null }, { "claim_id": "EMN-C05", "claim": "The litigation-related public source located for this ledger described crowdfunding to finance a contemplated lawsuit.", "status": "supported_public_reporting", "evidence_ids": [ "EMN-04" ], "qualification": null }, { "claim_id": "EMN-C07", "claim": "A complete public on-chain reconciliation of the exploit, returned funds, multisig transfer, claimant methodology, and distributions is not yet included.", "status": "requires_reconciliation", "evidence_ids": [ "EMN-03" ], "qualification": null } ], "accountability": [ "Deploying publicly callable pre-production contracts on mainnet created a foreseeable discovery and interaction risk.", "Public discussion or signaling around unfinished work can function as practical promotion even without an official launch announcement.", "The absence of an official interface or sale does not eliminate the real losses suffered by third parties.", "The strongest credible position acknowledges inadequate pre-release safeguards while correcting claims of an intentional withdrawal or a proven filed lawsuit." ], "last_reviewed": "2026-06-20" }, { "project_id": "fantom-sonic", "name": "Fantom / Sonic Labs", "canonical_path": "/public-record/fantom-sonic/", "relationship_type": "technical adviser, research contributor, director, and later CTO", "period": "2018–2026", "safe_public_summary": "Andre joined Fantom after formation and was publicly identified in 2018 as a Technical Advisor. He co-authored Fantom/Lachesis research, helped establish technical teams, later became a director, and in August 2024 became Sonic Labs CTO with responsibility for leading development of the Sonic network and Sonic Gateway. Sonic has publicly stated that he did not design the original 2018 Fantom tokenomics. A separate successful 2025 governance proposal nevertheless documents material post-launch token-policy and treasury activity, including strategic DeFi activity led by Andre. He resigned from the board in June 2026 and no longer makes business decisions for Sonic Labs. The current public record does not independently allocate every migration, airdrop, or launch-tokenomics decision.", "claims": [ { "claim_id": "FTM-C01", "claim": "The earliest official Fantom source in this ledger identifies Andre as a Technical Advisor in 2018, not as the project's original founder.", "status": "verified_public_record", "evidence_ids": [ "FTM-01" ], "qualification": null }, { "claim_id": "FTM-C02", "claim": "Andre was a co-author of public Fantom/Lachesis technical research in 2018 and 2021.", "status": "verified_public_record", "evidence_ids": [ "FTM-02", "FTM-04" ], "qualification": null }, { "claim_id": "FTM-C03", "claim": "Fantom stated in 2022 that Andre helped establish its development team but was not the sole or core developer of the Fantom technology stack.", "status": "verified_public_record", "evidence_ids": [ "FTM-03" ], "qualification": null }, { "claim_id": "FTM-C04", "claim": "By August 2024 Andre was a Sonic Labs director and became CTO, with an express mandate to lead design and development of the Sonic network, especially Sonic Gateway.", "status": "verified_public_record", "evidence_ids": [ "SNC-01" ], "qualification": null }, { "claim_id": "FTM-C05", "claim": "Sonic Labs publicly stated that Andre did not design the original 2018 Fantom tokenomics.", "status": "verified_public_record", "evidence_ids": [ "SNC-02" ], "qualification": "This addresses original Fantom tokenomics, not every later Sonic token-policy proposal." }, { "claim_id": "FTM-C06", "claim": "A successful 2025 governance proposal publicly proposed material issuance and fee/burn changes and described strategic DeFi activity led by Andre as the source of most tokens then held by Sonic Labs.", "status": "verified_public_record", "evidence_ids": [ "SNC-03" ], "qualification": "This establishes material involvement in post-launch treasury/token-policy activity; it does not establish sole authorship of all Sonic tokenomics." }, { "claim_id": "FTM-C07", "claim": "Andre, Michael Kong, and David Richardson resigned from the Sonic Labs board on June 19, 2026; Sonic said they would no longer make business decisions for the organization.", "status": "verified_public_record", "evidence_ids": [ "SNC-04" ], "qualification": null }, { "claim_id": "FTM-C08", "claim": "The public sources in this ledger do not independently establish who designed, approved, or operationally executed every element of the FTM-to-S migration, Sonic airdrop, or launch tokenomics.", "status": "not_publicly_established", "evidence_ids": [ "SNC-01", "SNC-03", "SNC-04" ], "qualification": null }, { "claim_id": "FTM-C09", "claim": "Andre's exact historical and current S/FTM holdings, company or foundation interests, compensation, severance, and transaction activity around the resignation are not established by this public-source set.", "status": "not_publicly_established", "evidence_ids": [], "qualification": null } ], "accountability": [ "Andre had substantial technical authorship and later formal board and CTO responsibility.", "His public prominence and executive role made him an organizational representative even for initiatives he did not personally design.", "The 2025 governance record prevents an overbroad claim that Andre had no role in token-policy or treasury matters.", "The correct distinction is phase- and decision-specific: original Fantom tokenomics, Sonic launch mechanics, and later post-launch governance are different subjects." ], "last_reviewed": "2026-06-20" }, { "project_id": "solidly", "name": "Solidly / ve(3,3)", "canonical_path": "/public-record/solidly/", "relationship_type": "protocol designer and original developer", "period": "2021–2022 original Fantom deployment", "safe_public_summary": "Andre Cronje designed and led the original Solidly deployment on Fantom. His January 2022 launch post documented an initial distribution of locked governance positions to qualifying Fantom projects, collectively representing 25% of the protocol in perpetuity, with emissions beginning after deployment. Following the March 2022 departure announcement, Solidex publicly said it would maintain the interface and that the contracts would continue. This record does not yet establish Andre's complete SOLID holdings, sales, affiliated allocations, or every historical admin right.", "claims": [ { "claim_id": "SLD-C01", "claim": "Andre publicly documented and led preparation of the original Solidly deployment on Fantom.", "status": "qualified_first_party_record", "evidence_ids": [ "SLD-01" ], "qualification": null }, { "claim_id": "SLD-C02", "claim": "The initial design allocated locked veNFT positions to qualifying recipient projects.", "status": "qualified_first_party_record", "evidence_ids": [ "SLD-01" ], "qualification": null }, { "claim_id": "SLD-C03", "claim": "The public launch post stated that recipient projects collectively would own 25% of the protocol in perpetuity and that token emissions would begin two weeks after deployment.", "status": "qualified_first_party_record", "evidence_ids": [ "SLD-01" ], "qualification": null }, { "claim_id": "SLD-C04", "claim": "After the March 2022 departure announcement, Solidex publicly announced arrangements to maintain the user interface and said the underlying contracts would continue operating.", "status": "verified_public_record", "evidence_ids": [ "SLD-02", "SLD-03" ], "qualification": "This is a maintainer statement; a separate source-code/proxy analysis is needed to prove the exact immutability and admin state." }, { "claim_id": "SLD-C05", "claim": "The current public-source set does not establish Andre's complete SOLID holdings, sales, allocations through affiliated protocols, compensation, or all historical admin rights.", "status": "not_publicly_established", "evidence_ids": [], "qualification": null }, { "claim_id": "SLD-C06", "claim": "A source-code and on-chain analysis is required before asserting that no person could alter, pause, migrate, or otherwise influence every relevant Solidly component.", "status": "requires_reconciliation", "evidence_ids": [ "SLD-01", "SLD-03" ], "qualification": null } ], "accountability": [ "Andre designed the mechanism, launch process, and initial project allocation model.", "The abrupt 2022 contributor departure had foreseeable reputational and market consequences even if contracts continued.", "A protocol contract continuing to execute is different from the continued operation of interfaces, APIs, governance, documentation, and ecosystem support." ], "last_reviewed": "2026-06-20" }, { "project_id": "multichain-relationship", "name": "Multichain — relationship and 2023 failure", "canonical_path": "/public-record/multichain/", "relationship_type": "third-party infrastructure relationship through Fantom; not an Andre-founded project", "period": "Relationship predates 2022; crisis and recovery efforts 2023 onward", "safe_public_summary": "Multichain was a third-party bridge with its own team, not a project founded or operated by Andre Cronje. Fantom publicly stated in 2022 that Multichain had operated independently for years. After the 2023 failure, Fantom sued Multichain Foundation in Singapore and pursued liquidation and asset recovery. The published judgment record described Multichain's CEO as having ultimate privileges over bridge assets. A complete accountability record should still disclose Fantom's original due diligence, integration decision, and Andre's role in endorsing or managing the relationship.", "claims": [ { "claim_id": "MCH-C01", "claim": "Fantom publicly stated in March 2022 that Multichain had its own team and had operated independently for years.", "status": "verified_public_record", "evidence_ids": [ "MCH-01" ], "qualification": null }, { "claim_id": "MCH-C02", "claim": "The 2024 Singapore litigation was brought by Fantom Foundation against Multichain Foundation, with Fantom presenting itself as a party that suffered loss.", "status": "verified_public_record", "evidence_ids": [ "MCH-02", "MCH-03", "MCH-04" ], "qualification": null }, { "claim_id": "MCH-C03", "claim": "The published judgment excerpt described Multichain's CEO as having ultimate privileges and control over bridge assets, contrary to representations about distributed MPC control.", "status": "verified_public_record", "evidence_ids": [ "MCH-03", "MCH-04" ], "qualification": null }, { "claim_id": "MCH-C04", "claim": "Fantom pursued a liquidator and recovery process after the failure.", "status": "verified_public_record", "evidence_ids": [ "MCH-02", "MCH-03" ], "qualification": null }, { "claim_id": "MCH-C05", "claim": "The public record in this ledger does not establish Andre as a Multichain founder, director, employee, bridge-key holder, or controller.", "status": "not_publicly_established", "evidence_ids": [ "MCH-01", "MCH-03" ], "qualification": "This is an absence in the identified record, not a universal proof of no relationship or influence." }, { "claim_id": "MCH-C06", "claim": "The ledger does not yet document Fantom's original technical due diligence, endorsement process, integration decisions, or Andre's role in selecting and promoting Multichain.", "status": "requires_reconciliation", "evidence_ids": [], "qualification": null } ], "accountability": [ "As a prominent Fantom adviser/director and spokesperson, Andre may fairly be asked what due diligence supported reliance on Multichain.", "Being a victim of a third-party failure does not eliminate responsibility for integration, risk management, user warnings, or contingency planning.", "The public record strongly distinguishes Multichain operational control from Fantom's ecosystem relationship, but a complete record should also document the partnership decision." ], "last_reviewed": "2026-06-20" }, { "project_id": "flying-tulip", "name": "Flying Tulip", "canonical_path": "/public-record/flying-tulip/", "relationship_type": "founder and current project lead", "period": "2025 onward", "safe_public_summary": "Andre Cronje is the founder of Flying Tulip. The project announced a $200 million private-round commitment in September 2025; its February 20, 2026 update reported $183,897,578.66 funded/currently held across tranches after refunds, exits, and withdrawals. The team receives no initial token allocation, but published tokenomics provide team economics through protocol-revenue-funded buybacks and unlocks. Flying Tulip is not adminless: its docs publicly identify privileged roles, multisig thresholds, proxies, configurator powers, and circuit breakers. These records should be refreshed on a recurring basis as funded capital, signers, contracts, and controls change.", "claims": [ { "claim_id": "FT-C01", "claim": "Andre is publicly identified as Flying Tulip's founder.", "status": "verified_public_record", "evidence_ids": [ "FT-01" ], "qualification": null }, { "claim_id": "FT-C02", "claim": "Flying Tulip announced a $200 million private-round commitment in September 2025.", "status": "verified_public_record", "evidence_ids": [ "FT-01" ], "qualification": "Later funded/currently held capital differed because commitments did not all fund and participants could exit." }, { "claim_id": "FT-C03", "claim": "The official February 20, 2026 update reported $183,897,578.66 funded/currently held across tranches, net of refunds, exits, and withdrawals.", "status": "verified_public_record", "evidence_ids": [ "FT-02" ], "qualification": "This was a point-in-time first-party accounting figure with public verification links; live values can differ." }, { "claim_id": "FT-C04", "claim": "The team receives no initial token allocation.", "status": "verified_public_record", "evidence_ids": [ "FT-01" ], "qualification": "This does not mean the team has no economics." }, { "claim_id": "FT-C05", "claim": "Published tokenomics provide team economics through protocol-revenue-funded buybacks and a disclosed Foundation/Team/Incentive unlock structure.", "status": "verified_public_record", "evidence_ids": [ "FT-01", "FT-04" ], "qualification": null }, { "claim_id": "FT-C06", "claim": "FT has a fixed pre-minted supply of 10 billion tokens and the docs describe an on-chain redemption right for eligible primary-sale positions.", "status": "verified_public_record", "evidence_ids": [ "FT-03" ], "qualification": null }, { "claim_id": "FT-C07", "claim": "Flying Tulip has privileged roles, proxy/admin functions, and safety controls rather than being adminless.", "status": "verified_public_record", "evidence_ids": [ "FT-05", "FT-06", "FT-07" ], "qualification": null }, { "claim_id": "FT-C08", "claim": "The published control registry includes a 3-of-5 multisig/treasury, a 3-of-4 configurator, and a 2-of-5 yield claimer, with addresses publicly disclosed.", "status": "verified_public_record", "evidence_ids": [ "FT-06" ], "qualification": null }, { "claim_id": "FT-C09", "claim": "The current public record does not fully establish Andre's personal compensation, beneficial interests in operating entities, later market purchases, or all signer identities.", "status": "not_publicly_established", "evidence_ids": [], "qualification": null } ], "accountability": [ "Andre is the founder and current public project lead, so product, fundraising, disclosure, and control architecture are appropriately attributed to him and the team.", "The accurate funding description distinguishes commitments, gross subscriptions, funded capital, current holdings, and refunded/exited capital.", "'No initial team allocation' must always be paired with the disclosed revenue-funded team unlock mechanism.", "Privileged roles and proxies should be treated as active governance and operational responsibility, not hidden behind decentralization language." ], "last_reviewed": "2026-06-20" } ] }