Risks and limitations
Walls are ETH-funded LP positions. Their presence defines available liquidity without making a trade’s outcome independent of the price, fees or pool state.
Price and execution
A position can be consumed. The market, target for new funds, price of a range and net amount from a sale are separate data. Use a quote for the intended amount.
A large change between quote and execution may cause rejection by the minimum received or input cap. Taxes, pool fees and gas remain real costs.
Contracts and accounting
Account separation must remain valid after purchases, sales, burns, fee collection, rewards, referrals and replacements. In particular, the new policy must preserve each wall’s ticks and remainders.
Isolating absorbed CUBIT before any possible resale is a critical constraint. It must be validated on the new position structure and exact-input/output paths, including when several operations follow each other.
Linking BandLib and WallLib, contract sizes and compilation settings are also within the verification scope.
Maintenance and availability
A keeper must pay gas and submit a transaction to perform maintenance. A low bounty, unavailable RPC, congestion or nonce tracking issue can delay it.
The guardian pause does not block swaps, but it can suspend the two maintenance functions during the authorized period. Pause expiry does not refill a spent reserve.
Integrations and modules
A third-party router does not necessarily handle the final burn the same way as the CUBIT router. Aggregator compatibility must be tested with hook taxes and the pool version.
Replaceable modules introduce trust in the team’s future decisions. Getter checks do not prove the safety of the chosen code. A new address requires a new review of the approval or signature.
Frontend and data
A display can use a simulation, old manifest or stale data. The interface must identify the network and blocks, flag outages and prevent signing from a context that has become inconsistent.
USD figures also depend on the capitalization convention and chosen conversion. The requested 7k base must be calibrated before becoming an ETH launch parameter.
What tests establish
Tests and invariant campaigns provide evidence for the cases, states and revision actually explored. Static analysis without High alerts does not mean no defects; a long successful campaign is not a general formal proof.
This edition claims neither a completed external audit, mainnet validation nor the impossibility of loss. Actual version status details what has been reported and what remains to be established.
Sources: audit/reports/2026-09-10-v1-v2/BILAN_FINAL_FR.md, SECURITE_ET_RECETTE.md, contracts/docs/STRICT_BURN.md and execution boundaries in the code.