Skip to content

LibraryMarkets2022Design paperCorpus record

1inch Fusion: resolvers filling signed swap orders

1inch. 1inch.

1inch's Fusion design publishes a signed swap that resolvers fill, instead of sending the user's market order straight into a pool.

A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.

1inch's Fusion design publishes a signed swap that resolvers fill, instead of sending the user's market order straight into a pool.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
1

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.

  1. Claim 01 · Paper model

    The defect

    An aggregator that also runs an intent system has two designs. Cite the one that actually moved the tokens.

  2. Claim 02 · Paper model

    The proposal

    1inch's Fusion design publishes a signed swap that resolvers fill, instead of sending the user's market order straight into a pool.

  3. Claim 03 · Paper model

    The mechanism

    The user signs a minimum result. A resolver posts the fill. The settlement contract is what binds the two.

  4. Claim 04 · Paper model

    The bound

    No volume share 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.

  1. 01 The defect

    Observation

    What the study says

    An aggregator that also runs an intent system has two designs. Cite the one that actually moved the tokens.

    Model

    What has to hold

    You are reading 1inch's protocol docs. A quote on a website may be either design.

    Falsifier

    What would retire it

    Does the document in front of you describe a resolver auction or a pool route?

  2. 02 The proposal

    Observation

    What the study says

    1inch's Fusion design publishes a signed swap that resolvers fill, instead of sending the user's market order straight into a pool.

    Model

    What has to hold

    You are reading 1inch's protocol docs. A quote on a website may be either design.

    Falsifier

    What would retire it

    What signature does the contract require?

  3. 03 The mechanism

    Observation

    What the study says

    The user signs a minimum result. A resolver posts the fill. The settlement contract is what binds the two.

    Model

    What has to hold

    No price, supply, yield, or adoption figure is added by this desk.

    Falsifier

    What would retire it

    Does the document in front of you describe a resolver auction or a pool route?

  4. 04 The bound

    Observation

    What the study says

    No volume share is stated here.

    Model

    What has to hold

    You are reading 1inch's protocol docs. A quote on a website may be either design.

    Falsifier

    What would retire it

    Does the document in front of you describe a resolver auction or a pool route?

03 Sequence

One action, as an operating tape

  1. 01The user signs a minimum result. A resolver posts the fill. The settlement contract is what binds the two.
  2. 02A classic aggregator route through pools is a different path. It does not become Fusion because the same brand displayed it.
  3. 03Resolver inventory is credit. The user is not paid until the fill transaction succeeds.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    1inch's Fusion design publishes a signed swap that resolvers fill, instead of sending the user's market order straight into a pool.

    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.

  2. What actually moves

    The cut

    A classic aggregator route through pools is a different path. It does not become Fusion because the same brand displayed 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.

  3. What a later deployment may change

    The cut

    Resolver inventory is credit. The user is not paid until the fill transaction succeeds.

    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 resolver set can be permissioned. If the docs say so, that is the liveness assumption.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading 1inch's protocol docs. A quote on a website may be either design.

  • 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 statement about any token listed in a router.

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

  1. 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 aggregator that also runs an intent system has two designs. Cite the one that actually moved the tokens.

What the design proposes

  • The user signs a minimum result. A resolver posts the fill. The settlement contract is what binds the two.
  • A classic aggregator route through pools is a different path. It does not become Fusion because the same brand displayed it.
  • Resolver inventory is credit. The user is not paid until the fill transaction succeeds.

How the mechanism is specified

  • The user signs a minimum result. A resolver posts the fill. The settlement contract is what binds the two.
  • A classic aggregator route through pools is a different path. It does not become Fusion because the same brand displayed it.
  • Resolver inventory is credit. The user is not paid until the fill transaction succeeds.

What this page does not treat as proven

  • No volume share is stated here.
  • A resolver set can be permissioned. If the docs say so, that is the liveness assumption.
  • This is not a statement about any token listed in a router.

Why the desk still reads it

1inch's Fusion design publishes a signed swap that resolvers fill, instead of sending the user's market order straight into a pool.

09 Lexicon

Terms, opened into the record

Resolver
A filler authorised, in the docs, to settle Fusion orders.
Aggregation route
A path through other pools. It is not an intent fill.

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

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.