LibraryInteroperability2021Design paperCorpus record
Connext Amarok: modular cross-chain transfers
Connext. Connext.
Connext publishes cross-chain transfers where liquidity is fronted on the destination and repaid when the origin message is authenticated by the messaging layer the docs select.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Connext publishes cross-chain transfers where liquidity is fronted on the destination and repaid when the origin message is authenticated by the messaging layer the docs select.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 0
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
The messaging layer is the security. Connext's routers are the liquidity. Citing one without the other describes a brand.
Claim 02 · Paper model
The proposal
Connext publishes cross-chain transfers where liquidity is fronted on the destination and repaid when the origin message is authenticated by the messaging layer the docs select.
Claim 03 · Paper model
The mechanism
A router fronts destination funds. Repayment follows the message.
Claim 04 · Paper model
The bound
No volume 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
The messaging layer is the security. Connext's routers are the liquidity. Citing one without the other describes a brand.
Model
What has to hold
You are reading Connext's docs. The configured message layer is part of the answer.
Falsifier
What would retire it
Which messaging layer authenticates the origin?
02 The proposal
Observation
What the study says
Connext publishes cross-chain transfers where liquidity is fronted on the destination and repaid when the origin message is authenticated by the messaging layer the docs select.
Model
What has to hold
You are reading Connext's docs. The configured message layer is part of the answer.
Falsifier
What would retire it
Which messaging layer authenticates the origin?
03 The mechanism
Observation
What the study says
A router fronts destination funds. Repayment follows the message.
Model
What has to hold
You are reading Connext's docs. The configured message layer is part of the answer.
Falsifier
What would retire it
Who loses money if the message never arrives?
04 The bound
Observation
What the study says
No volume is stated here.
Model
What has to hold
You are reading Connext's docs. The configured message layer is part of the answer.
Falsifier
What would retire it
Which messaging layer authenticates the origin?
03 Sequence
One action, as an operating tape
- 01A router fronts destination funds. Repayment follows the message.
- 02The message layer might be a configuration. If it changes, the trust assumption changes. The docs have to name the current one.
- 03A slow path that does not need a router, if documented, is the exit when liquidity refuses.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Connext publishes cross-chain transfers where liquidity is fronted on the destination and repaid when the origin message is authenticated by the messaging layer the docs select.
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
This is not Hop and not Across, though all three front liquidity.
What actually moves
The cut
The message layer might be a configuration. If it changes, the trust assumption changes. The docs have to name the current one.
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
A slow path that does not need a router, if documented, is the exit when liquidity refuses.
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
This is not Hop and not Across, though all three front liquidity.
05 Register
What has to be true
Network · Not re-measured
You are reading Connext's docs. The configured message layer is part of the answer.
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
A router can censor a fast transfer. That is liveness of the fast path.
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
The messaging layer is the security. Connext's routers are the liquidity. Citing one without the other describes a brand.
What the design proposes
- A router fronts destination funds. Repayment follows the message.
- The message layer might be a configuration. If it changes, the trust assumption changes. The docs have to name the current one.
- A slow path that does not need a router, if documented, is the exit when liquidity refuses.
How the mechanism is specified
- A router fronts destination funds. Repayment follows the message.
- The message layer might be a configuration. If it changes, the trust assumption changes. The docs have to name the current one.
- A slow path that does not need a router, if documented, is the exit when liquidity refuses.
What this page does not treat as proven
- No volume is stated here.
- This is not Hop and not Across, though all three front liquidity.
- A router can censor a fast transfer. That is liveness of the fast path.
Why the desk still reads it
Connext publishes cross-chain transfers where liquidity is fronted on the destination and repaid when the origin message is authenticated by the messaging layer the docs select.
09 Lexicon
Terms, opened into the record
- Router
- A liquidity provider who fronts the destination transfer.
- Messaging layer
- The system that authenticates the origin event. It is the security assumption.
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.
No repository match in this text.
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.