Skip to content
Blockchain LabBlockchain LabTHE VENTURE STUDIO

LibraryMarkets2017Design paperCorpus record

URL Format for Transaction Requests

ERC 681. Daniel A. Nagy.

ERC 681, URL Format for Transaction Requests. A standard way of representing various transactions, especially payment requests in ether and ERC-20 tokens as URLs.

Status in the source: Final. A reading of the public specification, not a copy of it and not a certification.

URL Format for Transaction Requests is worth reading for the rule it actually adds: A standard way of representing various transactions, especially payment requests in ether and ERC-20 tokens as URLs.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
4

Code

Source, repository, and what is actually hosted

  • ERC 681https://eips.ethereum.org/EIPS/eip-681
  • The source URL is not a GitHub repository. No code remote is invented.
  • Full text is not mirrored. Public availability is not a licence to copy the file onto this site.
  • Add to a reading list

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 rule

    A standard way of representing various transactions, especially payment requests in ether and ERC-20 tokens as URLs.

  2. Claim 02 · Paper model

    What was already failing

    A token that each contract invents from scratch does not transfer, approve, or display in any other contract. The cost of a shared interface is that the interface's holes become everyone's holes.

  3. Claim 03 · Paper model

    What the number does not mean

    The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

  4. Claim 04 · Paper model

    What a builder should be able to point at

    An implementation either constrains URL, ABI or it is a different design.

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 rule

    Observation

    What the study says

    A standard way of representing various transactions, especially payment requests in ether and ERC-20 tokens as URLs.

    Model

    What has to hold

    The standard does not enforce royalties, identity, or a price. If the transfer function does not check it, the chain will not.

    Falsifier

    What would retire it

    Which function in URL Format for Transaction Requests actually moves or approves value?

  2. 02 What was already failing

    Observation

    What the study says

    A token that each contract invents from scratch does not transfer, approve, or display in any other contract. The cost of a shared interface is that the interface's holes become everyone's holes.

    Model

    What has to hold

    The standard does not enforce royalties, identity, or a price. If the transfer function does not check it, the chain will not.

    Falsifier

    What would retire it

    What happens on a callback, a zero amount, or a contract recipient that rejects?

  3. 03 What the number does not mean

    Observation

    What the study says

    The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

    Model

    What has to hold

    You are implementing ERC 681 at the status the text itself states: Final.

    Falsifier

    What would retire it

    Which names does the text commit to: URL, ABI?

  4. 04 What a builder should be able to point at

    Observation

    What the study says

    An implementation either constrains URL, ABI or it is a different design.

    Model

    What has to hold

    You are implementing ERC 681 at the status the text itself states: Final.

    Falsifier

    What would retire it

    Which function in URL Format for Transaction Requests actually moves or approves value?

03 Sequence

One action, as an operating tape

  1. 01Open ERC 681 and read the status line before the examples.
  2. 02Write down the rule in one sentence. A fair version of that sentence is: A standard way of representing various transactions, especially payment requests in ether and ERC-20 tokens as URLs.
  3. 03Name the object that changes: URL, ABI.
  4. 04Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the text is allowed to settle

    The cut

    Ethereum Request for Comment 681 can settle the shape of URL Format for Transaction Requests. It cannot settle whether a later client, a later fork, or a later wallet still does this.

    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

    An application standard is not consensus. A contract can ignore it and still be a valid account.

  2. What this page will not pretend

    The cut

    There is no benchmark, no adoption number, and no claim that the mechanism is safe outside the assumptions written in the source.

    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 source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

05 Register

What has to be true

  • Model · Not re-measured

    You are implementing ERC 681 at the status the text itself states: Final.

  • Model · Not re-measured

    The object that has to change is URL, ABI. A neighbouring document with a similar name is not this one.

  • Model · Not re-measured

    The standard does not enforce royalties, identity, or a price. If the transfer function does not check it, the chain will not.

06 Divergence

What happened after the paper

The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

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

  4. 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

A token that each contract invents from scratch does not transfer, approve, or display in any other contract. The cost of a shared interface is that the interface's holes become everyone's holes.

What the design proposes

  • A standard way of representing various transactions, especially payment requests in ether and ERC-20 tokens as URLs.
  • URLs embedded in QR-codes, hyperlinks in web-pages, emails or chat messages provide for robust cross-application signaling between very loosely coupled applications.
  • A standardized URL format for payment requests allows for instant invocation of the user's preferred wallet application (even if it is a webapp or a swarm đapp), with the correct parameterization of the payment transaction only to be confirmed by the (authenticated) user.

How the mechanism is specified

  • Taken from the specification, the next constraint is: URLs embedded in QR-codes, hyperlinks in web-pages, emails or chat messages provide for robust cross-application signaling between very loosely coupled applications.
  • Locate URL, ABI in ERC 681 and apply it to one transaction or call.
  • Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

  • An application standard is not consensus. A contract can ignore it and still be a valid account.
  • The standard does not enforce royalties, identity, or a price. If the transfer function does not check it, the chain will not.
  • The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why the desk still reads it

Use ERC 681 when a pitch says 'URL Format for Transaction Requests' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.

09 Lexicon

Terms, opened into the record

ERC 681
The public text titled URL Format for Transaction Requests.
Final
The document's own label for how finished the text is. It is not a market fact.

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.

Protocols

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.