Roadmap

Ordered by dependency, not by date

Dates on a crypto roadmap are decoration. They slip, and the slip becomes the story. What follows is the order the work has to happen in, and the gate that must close before each phase can start. Nothing here is a delivery commitment.

Phase 0Complete

Token layer, audited and green

The token, vesting, airdrop distributor, treasury and buyback are written, internally audited, fixed and covered by a passing test suite.

Fixed-supply token with no mint, no owner, no pause
Buyback rewritten to perform a real swap and a real burn
Vesting cliff mathematics corrected and pinned by tests
Deploy script distributes the whole supply atomically and asserts the deploy key ends with nothing
Every finding published, including the unresolved ones

Phase 1In progress

Vault layer remediation

The vault contracts have one critical and two high findings open. Nothing else ships until they are closed, because everything else depends on deposits being safe.

Fix the yield vault so deposits reach the adapter its share price is measured against
Repair the EIP-712 signed rebalance path and its four failing tests
Repair the reputation registry publish and challenge flows
Make the invariant suite fail on a 100% revert rate instead of passing vacuously
Re-enable deposits in the portal only once the suite is green

Gate to the next phase

Full test suite green, zero critical or high findings open.

Phase 2Next

Third-party audit and testnet launch

Before any real money is involved, the contracts go to an external firm, and those findings get published in full the same way the internal ones were.

External audit of the token and vault layers
Public testnet with real managers signing real rebalances
Seat a multi-key oracle updater set and raise the median quorum
Season 1 snapshot criteria published before the snapshot is taken

Gate to the next phase

External audit report published, including any accepted risks.

Phase 3Next

Mainnet and token launch

Deployment, distribution, and liquidity. The float is set at launch and the insider tranches do not begin unlocking for twelve months.

Mainnet deployment with governance handover asserted in the deploy transaction
Season 1 airdrop claims open
Protocol-owned liquidity paired into the primary market
Buyback swap route configured and the burn ledger live in the portal

Gate to the next phase

Audit remediation complete, governance Safe signers confirmed.

Phase 4Later

Governance and open vaults

Voting weight exists from day one, but a token that can vote without anywhere to vote is only half the feature. This phase builds the other half.

Governor contract wired to the existing timestamp-keyed checkpoints
Season-by-season ecosystem emissions voted rather than assumed
Manager bonding, so a manager has capital at risk alongside depositors
Permissionless vault creation behind a bond and a review period
ERC-7540 asynchronous deposits for strategies that cannot settle instantly

Explicitly deferred

Things we decided not to build yet

Cutting scope is the reason phase 0 is finished. These are tracked, not forgotten.

Manager bonding

Managers should have capital at risk. It needs a slashing design that cannot be gamed by self-dealing.

Permissionless vaults

Wanted, but a long tail of unreviewed strategies would undermine the one thing this protocol is for.

AI-signed rebalances

The signing path is agnostic about who holds the key. Marketing it before there is a track record would be backwards.

Cross-chain deployment

One chain, done properly, before several done partially.

How to check whether this page is honest

Phase 0 claims a passing token test suite and phase 1 claims the vault suite is failing. Both are checkable: clone the protocol repository and run the test suite. If this page and the output disagree, believe the output.