Four networks, one view
A global reserve view is only as complete as the networks it can read. Boli's v1 priority covers the four networks where the same economic value is most often represented more than once — and treats the bridges between them as inputs rather than exceptions.
Boli runs no chain of its own. Assets settle on the major networks they already live on — EVM, Solana, Stellar and Canton. Tenzro sits between them as a double-accounting layer and a buffer. Pilots read live mainnet contracts on Ethereum, Arbitrum and Solana, and two independent observers sign each epoch.
Supply is read where it lives.
Each supported network has its own observers reporting circulating supply for the registered representations on that network. The protocol does not depend on a single canonical chain — the global view is assembled from all of them.
Ethereum mainnet and the major L2s, where most multi-chain representations of an asset first appear.
SVM-native representations, read directly rather than inferred from bridge accounting.
Stellar asset representations, common for payment- and remittance-oriented issuance.
DAML-based representations on Canton, where sub-transaction privacy changes what a public observer can see.
Bridges are inputs, not afterthoughts.
Bridges, wrappers, and burn-and-mint mechanisms are exactly what create local views of supply in the first place. Treating them as first-class inputs is what allows the same economic value to be counted once globally, rather than once per network.
The home network holds the asset while a remote network issues against it. Boli reads the lockbox balance and subtracts it. WBTC on Arbitrum works this way, and the Ethereum-side lockbox is netted out every epoch.
The unit is destroyed on one network and recreated on another. Nothing is subtracted, and the declared route tells the observer the movement was a transfer.
Routes are part of the asset's registration. The protocol nets what an issuer declared and infers nothing.
CCIP, Wormhole, LayerZero and the rest are instances of these two mechanisms. Adding one is a matter of declaring the route on the asset, not integrating a vendor.
Coverage is a property of the asset, not the protocol.
An asset’s registration lists its representations — the network and contract address of each one — and the routes between them. Adding a network to an asset means adding a representation to that list. Nobody has to approve it, and no new protocol version is required.
An invariant holds across the networks an asset declares. A representation that was never registered is not in the total. The declared set is public, and it is the first thing to read.
Coverage is what makes the invariant meaningful.
An invariant that only holds on the networks you happen to be watching is not an invariant. Which networks an asset declares is part of its public record, and worth reading before relying on the total.