Reading dapp data
The Proof page helps reconcile displayed figures with protocol states and events. Start with the network, deployment, version and read block before interpreting an amount.
Figures to distinguish
| Data | What it describes |
|---|---|
| Market price | Current pool price, separate from the net result for a specific amount |
| Next target | Level calculated at time T for new funds; it is not yet a funded position |
| Active walls | Already funded positions, each with its ID, ticks and remaining liquidity |
| Pending ETH | Funds reserved for upcoming placements, not yet executable liquidity |
| A wall’s idle ETH | Remainder allocated to a particular wall, still attached to its ticks |
| Cushion | ETH actually deployed in the mobile ladder |
| Ladder idle ETH | Undeployed ladder funds, including reserves and rounding |
| Burn queue | Isolated CUBIT reserved exclusively for destruction |
| Total burned | CUBIT whose burn has actually reduced supply |
A wall’s level and its remaining ETH must be read together.
What changes with multiple walls
The old view showed a single wall. The new policy requires a list of positions and a separate target. A chart of the last funded wall can fall when new funds are placed at a lower target; older levels remain unchanged.
The historical name floorPrice must therefore not be read as a global market minimum. Its new meaning, intended for the last funded wall, is part of the revision awaiting validation.
The new fields and position discovery are detailed in integration. The current Sepolia frontend does not prove that this multiple-wall interface is already connected.
Gross price, net price and quote
A gross reference represents a position’s price level. A net reference can include a range boundary, LP fees, sell tax and an assumption about v4 protocol fees.
An actual sale depends on the amount, positions crossed, rounding and gas. A “net floor” reference is not a calculation of your wallet’s performance and does not replace a quote.
Data modes
| Display | Interpretation |
|---|---|
| On-chain, identified block | Data read from the indicated deployment |
| Loading | Initial read still incomplete |
| Stale data or RPC failure | Last known state; not authorization to sign |
| Simulation or demonstration | Local illustration of the mechanism |
For future releases, check announced availability and the addresses of modules offered to the user.
Repeating the verification
Check the identities of the token, hook and pool, then the registry’s current modules and its moduleRevision. Reconcile events with the transaction hash and their canonical block.
The Keepers and Proof pages track maintenance, taxes and burns. A screenshot or old report cannot replace this version identification. Actual version status.
Sources: CubitLens.sol, interfaces/ICubitLens.sol, dapp/src/chain/snapshot.ts, releases.ts, events.ts and components/Header.tsx.