Q markBridgePools And Reserve Ledger

Pools And Reserve Ledger

Bridge can name what kind of value record is being handled: protocol inventory, user bonded value, assigned host vault, fee category, reserve buffer, receipt, refusal, or quarantine. These are ledger categories, not live balance claims.

Ledger Categories

Public labels that make Bridge easier to review without publishing private procedure.

Protocol inventory pool

Inventory Bridge may use to satisfy an approved native acquisition lane before fresh sourcing is required.

User bonded pool

Request-linked value held for an acquisition, quote, or route decision.

Assigned host vault

The host-chain account or vault label tied to a request or lane.

Host-fee ledger

Gas, miner fee, rent, relay submission, deployment, and host execution costs remain pass-through categories.

Reserve and finality buffer

Slippage, reorg/finality risk, dust, and safety posture stay visible as buffers, not yield or backing claims.

Route-output ledger

Output class and policy action are recorded before any destination can treat the output as meaningful.

Receipt and export ledger

Public-safe receipts and Infra export labels preserve reviewability without exposing private route procedure.

Refusal and quarantine ledger

Unsafe or unresolved records can stop, refund, refuse, or quarantine instead of being reinterpreted.

How To Read It

Ledger wording should reduce confusion, not imply more than Bridge has opened.

Pool labelNames where the request-linked value sits in Bridge accounting.Not admission
Reserve labelNames fee, buffer, or finality categories used for product safety.Not backing
Host vaultNames assignment posture on an outside ecosystem.Not control claim
ReceiptNames what Bridge observed, recorded, exported, or refused.Not truth itself
QuarantineNames unresolved, unsafe, mismatched, or blocked value posture.Not failure

Public Scope

  • Product accounting categories.
  • Receipt and export posture.
  • Route-output class and refusal state.
  • Closed public movement labels.

Public Boundary

  • No live balances unless an official live endpoint publishes them.
  • No redemption promise.
  • No Reserve backing claim.
  • No private signer, route, timing, key, or provider material.