Upcoming features
V2 extends the CUBIT market with four uses: depositing CUBIT to share LP revenue, referring users, observing the ladder and creating isolated child markets.
The features below are presented as future releases. Their availability will be specified at each release after their scope has been validated.
Release windows
| Feature | Target window | Planned use |
|---|---|---|
| mCUBIT Vault | From D+3 | CUBIT deposits with WETH rewards from realized LP fees |
| CUBIT Links | From D+5 | Signed referrals rewarded from the team share |
| Momentum | From D+7 | Viewing active allocations and ladder reserves |
| Curated Forge | From D+10 | Beta for creating isolated child markets |
Dates are roadmap milestones. They must not be presented as already established availability.
Sharing ladder revenue
The Vault plans a nontransferable deposit position, a 24-hour lock and WETH rewards. Funding comes from a share of LP fees actually realized in ETH; it does not require creating new CUBIT.
Developing referrals
Links plans a first-bound link accepted through a signature. Rewards come from the team share on referred swaps; the user’s total taxes remain unchanged.
Observing and creating
Momentum and Forge cover two distinct functions: viewing the ladder and launching child markets. Momentum remains read-only. Forge starts with a curated beta; any public opening is a later step.
Rights associated with modules
The team retains replacement powers over the protocol’s peripherals. These rights persist after the core maintenance guardian expires.
Replacement does not take the funds of an old Vault position or move the reserves of children already created. Each module offered to users must be identified and verified. Permissions and replacements.
The roadmap details the criteria associated with these releases.