Project Roles & Public Record

This section documents my role, authority, economic structure, and transition history across projects frequently associated with me.

It is not intended to erase criticism or imply that technical contributors carry no responsibility. Its purpose is to separate facts that are often conflated:

• Creating or designing a protocol.
• Forming a company or original token project.
• Holding a formal executive or board role.
• Controlling minting, treasury, upgrades, interfaces, or user assets.
• Receiving an initial allocation or later economic benefit.
• Leaving an active contributor role.
• Whether the underlying project continued independently.

I accept responsibility for the work, decisions, deployments, communications, and formal roles I actually led. Where broader conduct has been attributed to me, these pages identify what the public record does and does not establish.

Records

Yearn Finance

Creator and initial developer. The record covers YFI's initial distribution, the initial mint authority, its transfer to a multisig, and Yearn's later governance structure.

Keep3r Network

Creator and initial developer. The record covers the launch model, beta status, public code, and the limits of what public sources establish about later holdings and control.

Eminence

Developer of an unreleased experimental system. The record distinguishes pre-production mainnet deployment from an official launch and documents the exploit, returned funds, compensation reporting, and the limits of the litigation record.

Fantom and Sonic Labs

Technical advisor, research contributor, director, and later Chief Technology Officer. The record distinguishes original project formation, technical authorship, executive responsibility, original tokenomics, later token-policy involvement, and the 2026 board transition.

Solidly

Designer and original developer. The record covers the launch design, protocol allocations, the 2022 contributor departure, and publicly documented continuity of contracts and interfaces.

Multichain relationship

A related-infrastructure record rather than an Andre-founded project. It documents Multichain's independent operation, Fantom's integration relationship, the 2023 failure, and subsequent litigation and recovery efforts.

Flying Tulip

Founder and current project lead. The record covers funding terminology, token supply, team economics, redemption mechanics, privileged roles, multisigs, and current accountability.

Evidence standard

Each page gives priority to:

1. Court, governance, on-chain, contract, source-code, academic, and comparable public records.
2. Official project documentation and contemporaneous organizational announcements.
3. Contemporaneous independent reporting that quotes or links the underlying source.
4. First-person publications, clearly identified as such.

A first-party source is publicly inspectable, but it is not automatically an independent audit. Where the public record is incomplete, the page says so rather than substituting a categorical denial.

How to cite

Use the canonical page URL and the displayed Last reviewed date. Each material factual section links to the source records supporting it.

A machine-readable version is available at:

• /public-record/data.json
• /public-record/evidence.json

Corrections

For publisher-ready replacement wording and active factual corrections, see the Corrections & Documentary Record.

For the June 2026 Sonic Labs transition, see the board-resignation statement.

Change log

• 2026-06-20: Initial publication.