LibraryInteroperability2022Design paperCorpus record
Stargate: unified liquidity pools for cross-chain transfers
Stargate. Stargate.
Stargate publishes pools of a shared asset on several chains, so a transfer debits one pool and credits another, with a messaging layer underneath.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Stargate publishes pools of a shared asset on several chains, so a transfer debits one pool and credits another, with a messaging layer underneath.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 2
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
The defect
Unified liquidity is an accounting agreement between pools. If the message layer forks or stalls, the pools can disagree about who was paid.
Claim 02 · Paper model
The proposal
Stargate publishes pools of a shared asset on several chains, so a transfer debits one pool and credits another, with a messaging layer underneath.
Claim 03 · Paper model
The mechanism
A pool on each chain holds inventory. A transfer locks or burns on the source and pays from the destination pool.
Claim 04 · Paper model
The bound
No pool size is stated here.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 The defect
Observation
What the study says
Unified liquidity is an accounting agreement between pools. If the message layer forks or stalls, the pools can disagree about who was paid.
Model
What has to hold
You are reading Stargate's docs. The message layer is a separate assumption.
Falsifier
What would retire it
What message layer connects the pools in the deployment you mean?
02 The proposal
Observation
What the study says
Stargate publishes pools of a shared asset on several chains, so a transfer debits one pool and credits another, with a messaging layer underneath.
Model
What has to hold
You are reading Stargate's docs. The message layer is a separate assumption.
Falsifier
What would retire it
What message layer connects the pools in the deployment you mean?
03 The mechanism
Observation
What the study says
A pool on each chain holds inventory. A transfer locks or burns on the source and pays from the destination pool.
Model
What has to hold
The document is the one at the source URL. A marketing page with the same brand is not this text.
Falsifier
What would retire it
What happens if the destination pool has less inventory than the transfer?
04 The bound
Observation
What the study says
No pool size is stated here.
Model
What has to hold
You are reading Stargate's docs. The message layer is a separate assumption.
Falsifier
What would retire it
What message layer connects the pools in the deployment you mean?
03 Sequence
One action, as an operating tape
- 01A pool on each chain holds inventory. A transfer locks or burns on the source and pays from the destination pool.
- 02The delta algorithm, if the docs still name one, is how the pools stay balanced. It is a credit rule, not a price oracle.
- 03The messaging layer underneath is a dependency. In a deployment that uses LayerZero, that study applies. Do not skip it.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Stargate publishes pools of a shared asset on several chains, so a transfer debits one pool and credits another, with a messaging layer underneath.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
What actually moves
The cut
The delta algorithm, if the docs still name one, is how the pools stay balanced. It is a credit rule, not a price oracle.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
What a later deployment may change
The cut
The messaging layer underneath is a dependency. In a deployment that uses LayerZero, that study applies. Do not skip it.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
05 Register
What has to be true
Network · Not re-measured
You are reading Stargate's docs. The message layer is a separate assumption.
Model · Not re-measured
The document is the one at the source URL. A marketing page with the same brand is not this text.
Model · Not re-measured
No price, supply, yield, or adoption figure is added by this desk.
06 Divergence
What happened after the paper
This is not native USDC burn-and-mint. The inventory is the pool's.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
Unified liquidity is an accounting agreement between pools. If the message layer forks or stalls, the pools can disagree about who was paid.
What the design proposes
- A pool on each chain holds inventory. A transfer locks or burns on the source and pays from the destination pool.
- The delta algorithm, if the docs still name one, is how the pools stay balanced. It is a credit rule, not a price oracle.
- The messaging layer underneath is a dependency. In a deployment that uses LayerZero, that study applies. Do not skip it.
How the mechanism is specified
- A pool on each chain holds inventory. A transfer locks or burns on the source and pays from the destination pool.
- The delta algorithm, if the docs still name one, is how the pools stay balanced. It is a credit rule, not a price oracle.
- The messaging layer underneath is a dependency. In a deployment that uses LayerZero, that study applies. Do not skip it.
What this page does not treat as proven
- No pool size is stated here.
- A destination payout can fail if the pool is empty. The docs' instant-guarantee claim has to be read against that.
- This is not native USDC burn-and-mint. The inventory is the pool's.
Why the desk still reads it
Stargate publishes pools of a shared asset on several chains, so a transfer debits one pool and credits another, with a messaging layer underneath.
09 Lexicon
Terms, opened into the record
- Unified liquidity
- Pools on several chains that account as one book. They can still diverge if messages fail.
- Delta
- The documented imbalance between pools. It is an accounting object, not a fee by itself.
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
Concepts
Papers
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.