LibraryInteroperability2022Design paperCorpus record
Across: intents settled by a relayer and a settlement contract
Across Protocol. Across.
Across publishes an intent: a user names a destination fill, a relayer fills it, and a settlement contract later reimburses the relayer if the origin deposit checks out.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Across publishes an intent: a user names a destination fill, a relayer fills it, and a settlement contract later reimburses the relayer if the origin deposit checks out.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 5
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
An intent system is a credit extension by the relayer. If you ignore who waits to be repaid, you have missed the design.
Claim 02 · Paper model
The proposal
Across publishes an intent: a user names a destination fill, a relayer fills it, and a settlement contract later reimburses the relayer if the origin deposit checks out.
Claim 03 · Paper model
The mechanism
The user deposits on the origin. The relayer pays the user on the destination from its own inventory. Those are not the same coins moving.
Claim 04 · Paper model
The bound
No volume and no fee 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
An intent system is a credit extension by the relayer. If you ignore who waits to be repaid, you have missed the design.
Model
What has to hold
You are reading Across's docs. UMA's optimistic oracle, if used, is a dependency and a separate study.
Falsifier
What would retire it
What has to be true before that party is repaid?
02 The proposal
Observation
What the study says
Across publishes an intent: a user names a destination fill, a relayer fills it, and a settlement contract later reimburses the relayer if the origin deposit checks out.
Model
What has to hold
You are reading Across's docs. UMA's optimistic oracle, if used, is a dependency and a separate study.
Falsifier
What would retire it
What happens if the origin deposit is valid but no relayer fills?
03 The mechanism
Observation
What the study says
The user deposits on the origin. The relayer pays the user on the destination from its own inventory. Those are not the same coins moving.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
What happens if the origin deposit is valid but no relayer fills?
04 The bound
03 Sequence
One action, as an operating tape
- 01The user deposits on the origin. The relayer pays the user on the destination from its own inventory. Those are not the same coins moving.
- 02Repayment depends on the settlement rule the docs name, often an optimistic or oracle-checked verification. That rule is the trust assumption.
- 03A slow fill is a relayer choice or a liquidity limit, not a finality proof of the destination chain.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Across publishes an intent: a user names a destination fill, a relayer fills it, and a settlement contract later reimburses the relayer if the origin deposit checks out.
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
Repayment depends on the settlement rule the docs name, often an optimistic or oracle-checked verification. That rule is the trust assumption.
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
The verification method must be read from the current docs. It has changed before and can change again.
What a later deployment may change
The cut
A slow fill is a relayer choice or a liquidity limit, not a finality proof of the destination chain.
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
Model · Not re-measured
You are reading Across's docs. UMA's optimistic oracle, if used, is a dependency and a separate study.
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 a lock-and-mint bridge unless the page you opened says it is.
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
An intent system is a credit extension by the relayer. If you ignore who waits to be repaid, you have missed the design.
What the design proposes
- The user deposits on the origin. The relayer pays the user on the destination from its own inventory. Those are not the same coins moving.
- Repayment depends on the settlement rule the docs name, often an optimistic or oracle-checked verification. That rule is the trust assumption.
- A slow fill is a relayer choice or a liquidity limit, not a finality proof of the destination chain.
How the mechanism is specified
- The user deposits on the origin. The relayer pays the user on the destination from its own inventory. Those are not the same coins moving.
- Repayment depends on the settlement rule the docs name, often an optimistic or oracle-checked verification. That rule is the trust assumption.
- A slow fill is a relayer choice or a liquidity limit, not a finality proof of the destination chain.
What this page does not treat as proven
- No volume and no fee is stated here.
- The verification method must be read from the current docs. It has changed before and can change again.
- This is not a lock-and-mint bridge unless the page you opened says it is.
Why the desk still reads it
Across publishes an intent: a user names a destination fill, a relayer fills it, and a settlement contract later reimburses the relayer if the origin deposit checks out.
09 Lexicon
Terms, opened into the record
- Intent
- A signed request for an outcome, not a transaction that itself completes the outcome.
- Relayer inventory
- The capital a filler spends on the destination and later seeks back.
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.