Public record
Solidly: Protocol Design, Launch, and 2022 Transition
Summary
I designed and led preparation of the original Solidly deployment on Fantom.
My January 2022 launch publication described 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 stated that it would maintain the user interface and that the underlying contracts would continue operating.
This record does not establish my complete SOLID holdings, sales, affiliated allocations, compensation, or every historical administrative right.
Facts at a glance
| Question | Public record |
|---|---|
| What was my role? | Protocol designer and original developer. |
| How was the initial governance position distributed? | Locked veNFT positions were allocated to qualifying recipient projects. |
| What share did recipient projects collectively hold under the stated design? | 25% of the protocol in perpetuity. |
| Was launch conditioned on an audit? | The launch preparation post referred to a final pending audit. |
| Did everything necessarily stop when I left? | Solidex publicly said it would maintain the interface and that the contracts would continue operating. |
| Does this page establish my complete SOLID activity or every admin role? | No. |
Verified public record
Design and launch
My public launch-preparation record described:
- Deployment on Fantom mainnet.
- Locked veNFT positions allocated to qualifying recipient projects.
- Recipient projects collectively holding 25% of the protocol in perpetuity.
- Emissions beginning after deployment.
- A final pending audit before deployment.
This is a first-person primary record of the intended launch design. It is not an independent audit of implementation or allocation.
2022 transition and continuity
After the March 2022 departure announcement, Solidex publicly announced arrangements to maintain the Solidly interface and said the underlying contracts would continue operating.
A public Solidex repository documents continued interface work.
Contract execution, interface maintenance, APIs, documentation, governance, and ecosystem support are different layers. A complete record should identify what continued, changed, or stopped at each layer.
Responsibility I accept
- I designed the mechanism and original launch process.
- I selected and publicly described the initial allocation model.
- The abrupt departure had foreseeable reputational and market consequences.
- Continued contract execution does not remove responsibility for interface, communication, governance, and ecosystem disruption.
What the public record does not establish
The sources reviewed for this page do not establish:
- My complete SOLID holdings, sales, or compensation.
- Whether any affiliated protocol allocation created an indirect personal economic interest.
- Every deployer, owner, minter, voter, emergency, proxy, or administrative role.
- That all Solidly components and services were immutable.
- That no liquidity or treasury assets moved around the transition.
Sources
- SLD-01: Solidly: preparation for launch — Andre Cronje — 2022-01-25. Source tier D;
subject_authored_publication. - SLD-02: Solidly interface continuity statement — Solidex — 2022-03-06. Source tier B;
maintainer_announcement. - SLD-03: Solidly user-interface repository — Solidex. Source tier A;
source_code_repository.
Change log
- 2026-06-20: Initial publication.