Roadmap and release criteria
The schedule describes publication intent. Release cadence does not replace code validation. A feature that moves funds must be prepared, tested and accepted before opening.
The roadmapdev.md reference and historical dapp roadmap contain outdated rules. This page revisits milestones while distinguishing requested work from already attested versions.
The current prerequisite
The wall policy has changed: target LP fees of 0.01%, a target calculated at time T, older funds kept at their position’s ticks. This new version must complete validation and integration before another network acceptance test.
The 7k base must be converted and fixed under a clear ETH launch convention. No new deployment of this policy is attested in this edition.
Milestones
| Milestone | Function | Status and condition |
|---|---|---|
| D0 | V1 market | Old V1 on Sepolia; new multiple-wall policy under validation |
| D+2 | Keepers | Interface and service prepared around existing functions; continuous operations to establish |
| From D+3 | mCUBIT Vault | Future release: 24-hour lock, realized ETH LP fees, WETH rewards |
| From D+5 | CUBIT Links | Future release: first-bound signature, share taken from the team |
| From D+7 | Momentum | Future release: read-only ladder view |
| From D+10 | Curated Forge | Future isolated beta, subject to acceptance |
| Guardian expiry | End of maintenance pause power | Read guardianExpiry; 14 days after hook construction |
| D+21 | Possible public Forge | Not implemented; separate decision and code required |
V2 windows are milestones measured from launch. Availability will be specified for each release. The guardian follows its own expiry; team administration of modules continues afterward.
Conditions for opening the Vault
Reward accounting must survive deposit, withdrawal, claim, rounding and replacement tests, with zero CUBIT creation and no access to wall principal. Funding must come from ETH LP fees actually collected.
Conditions for opening Links
Total taxes must not increase. Signatures must commit to the correct trader, chain and registry. Another router must not be able to impersonate attribution context, and existing claims must survive router replacement.
Conditions for Momentum and Forge
Momentum must remain a view of the ladder. Forge must preserve child isolation, curated restrictions and template control. Public opening does not follow merely from elapsed time.
Conditions for a production version
The release must publish its identities, compilation parameters, linked libraries, expected bytecodes and permissions. Tests must cover the final sources and be linked to that release.
Real wallet workflows, aggregators, absorption, services and monitoring complement local tests. The historical Sepolia deployment does not automatically accept these new changes.
Historical announcements to reclassify
A “floor that only rises”, a breakeven crossing at a predetermined capitalization or “total immutability at D+14” do not describe the new policy and permissions.
Communications must indicate the funded wall, its current target, funds placed and protocol version. Historical results remain available as such in the sources.