Crosschain supply: remove duplicated economic claims
Crosschain supply research should count economic claims consistently instead of adding every token representation visible on every network. A locked origin asset and its destination representation can refer to the same underlying units. Preserve both technical balances, but do not automatically treat them as two independent supplies.
The Ethereum bridges documentation describes different bridge mechanisms and trust assumptions. A lock-and-mint example is useful for understanding duplication, while an actual investigation must establish the deployed mechanism. Not every crosschain token arrangement can be modeled with the same subtraction rule.
Choose the question before the total
A network-level token inventory asks what balances exist on that network. A consolidated economic-supply estimate asks how many distinct units or claims exist across the defined system. Both can be useful, but their denominators and adjustment rules differ.
List the origin asset, each representation, custody contracts, mint or burn relationships, and conversion rules. Record contract identities rather than only symbols. Build a dependency graph showing which representation is backed by which asset and whether another representation sits on top of it.
| Inventory line | Consolidation question |
|---|---|
| Origin issued units | What starting quantity is being counted? |
| Locked origin units | Are these backing a counted representation? |
| Destination representation | Which underlying claim does it represent? |
| Rewrapped representation | Is the claim already included at another layer? |
| Unmatched amount | Timing, coverage gap, or unexplained discrepancy? |
Keep a gross technical inventory alongside the adjusted economic view. That makes the adjustment inspectable and prevents readers from interpreting excluded balances as nonexistent.
Hypothetical one-hop bridge
Assume a fictional origin token has 100 million issued units. Twenty million are locked in a bridge, and the destination network has twenty million matching representations. Adding all displayed supplies gives 120 million. Under a simple one-to-one lock-and-mint model with matched observations, that would count the locked units and their representations twice.
One consistent economic view retains the 100 million origin units and treats the destination representation as a location or claim breakdown. Another presentation separates 80 million unbridged origin units and twenty million represented elsewhere. Both sum to 100 million under the stated assumptions.
Now suppose five million destination units are wrapped again in another application. Adding that receipt supply would create another layer of duplication. Trace the backing relationship before adding anything. All amounts are hypothetical and do not establish actual backing for any real deployment.
Reconcile timing and conversion
Capture observations close enough to support the intended comparison and record their exact times. Cross-network actions can pass through intermediate states. An unmatched mint and lock observed at different stages may be a timing issue, but the researcher must verify it rather than assuming every discrepancy is harmless.
Check conversion ratios and units. A representation need not always correspond to one identical unit, and a rebasing or exchange-rate mechanism can require a different normalization. State the deployed rule and avoid forcing every asset into the example’s one-to-one arithmetic.
Preserve unmatched amounts as unresolved items with an action: verify another network, inspect a contract, retrieve a missing interval, or locate migration documentation. Do not create an unexplained adjustment simply to produce the expected total. A balancing number can hide the very issue the research should expose.
Report three distinct outputs
Provide the gross network inventory, the dependency-adjusted estimate, and the unresolved reconciliation. Explain what each answers. This structure allows a reader studying network activity to use the gross data while a reader studying total economic supply can see the consolidation assumptions.
The method is incomplete when a proprietary mechanism, migration, or missing deployment registry prevents tracing claims. In that situation, report known relationships and avoid a precise consolidated total. A full balance match also does not establish bridge security or universal redemption access; those require separate investigation.
Common mistakes include adding every network’s headline supply, counting receipt layers as new assets, ignoring conversion ratios, and using mismatched observation times. This is a supply-definition exercise for spot research, not evidence of a future price path.
FAQ
Should bridged balances be removed from every dataset?
No. Keep them in the technical inventory. Apply a clearly documented adjustment only when answering a consolidated economic-supply question.
Does a matched consolidated total prove all representations are safe?
No. Reconciliation checks quantity relationships. Control, implementation, backing quality, and redemption conditions remain separate evidence tasks.