Momentum and Forge

These two modules have distinct roles: Momentum makes the ladder’s state visible, while Forge prepares the creation of isolated child markets.

Momentum: observing the market

Momentum is planned from D+7. It exposes a regime or a view of active allocations and ladder reserves based on the Lens.

It is a read-only feature, with no power to withdraw ETH from walls or change core rules. A transition between displayed regimes is not a trading command.

The actual geometry remains that of the hook. Any adaptation of this geometry must be part of the validated core version; a frontend component cannot invent it.

Forge: a curated beta

The targeted release window is D+10. The curated model reserves launches for the curator, the team address. It is not a public factory open to everyone.

Each child receives its own token and hook, pool identities and reserves. The hook creation template is controlled by a hash fixed in Forge’s constructor.

The name, symbol, roles, deployment salt and supplied code are checked. Creating a child grants no permission over the parent CUBIT pool.

The launch fee

The Forge fee is allocated to the parent hook’s wall reserve. It is an addition to the wall reserve, with no right to withdraw those funds.

The launchFee() amount is fixed when each Forge is constructed. The 0.01 ETH figure in earlier reports is a preparatory choice for that deployment; read the actual on-chain amount of the contract in use.

Older roadmap versions mention a choice between buy-and-burn and wall funding. The current specification chooses funding the wall reserve.

If Forge is replaced

Replacement changes the reference factory for future launches. Children already created retain their own contracts and funds.

The registry’s compatibility checks do not replace a review of the template and factory.

D+21 is a decision point

Opening a public factory at D+21 is not implemented. It is a conditional step, separate from the curated beta.

Acceptance of the beta, validation of isolation and an explicit choice of a public implementation are required before presenting this opening as available.

Sources: the repository’s current specification, periphery/CubitForge.sol, CubitV2.setForge and dapp/src/pages/Momentum.tsx.