Web3 URL to EVM Call Message Translation

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

   This standard translates an RFC 2396 URI like web3://uniswap.eth/ to an EVM message such as: EVMMessage { To: 0xaabbccddee....

2. Claim 02 · Paper model

   What was already failing

   An underpriced or ambiguous EVM rule is not a feature. It is a block that takes longer than the gas limit claimed, or a client that disagrees about the result.

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 RFC, URI, EVM 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

   This standard translates an RFC 2396 URI like web3://uniswap.eth/ to an EVM message such as: EVMMessage { To: 0xaabbccddee....

   Model

   What has to hold

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

   Falsifier

   What would retire it

   What does Web3 URL to EVM Call Message Translation charge, reject, or redefine on the first touch versus a later one?

2. 02 What was already failing

   Observation

   What the study says

   An underpriced or ambiguous EVM rule is not a feature. It is a block that takes longer than the gas limit claimed, or a client that disagrees about the result.

   Model

   What has to hold

   The object that has to change is RFC, URI, EVM. A neighbouring document with a similar name is not this one.

   Falsifier

   What would retire it

   Can you point at the object in a client: RFC, URI, EVM?

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 4804 at the status the text itself states: Final.

   Falsifier

   What would retire it

   Can you point at the object in a client: RFC, URI, EVM?

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

   Observation

   What the study says

   An implementation either constrains RFC, URI, EVM or it is a different design.

   Model

   What has to hold

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

   Falsifier

   What would retire it

   Can you point at the object in a client: RFC, URI, EVM?

03 Sequence

One action, as an operating tape

1. 01Open ERC 4804 and read the status line before the examples.
2. 02Write down the rule in one sentence. A fair version of that sentence is: This standard translates an RFC 2396 URI like web3://uniswap.eth/ to an EVM message such as: EVMMessage { To: 0xaabbccddee....
3. 03Name the object that changes: RFC, URI, EVM.
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 4804 can settle the shape of Web3 URL to EVM Call Message Translation. 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

   Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.

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

   A gas or opcode change is not a throughput benchmark. It is a relative price and a validity rule.

05 Register

What has to be true

• Model · Not re-measured

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

• Model · Not re-measured

  The object that has to change is RFC, URI, EVM. A neighbouring document with a similar name is not this one.

• Model · Not re-measured

  Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.

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

1. Kill test 1What does Web3 URL to EVM Call Message Translation charge, reject, or redefine on the first touch versus a later one?
2. Kill test 2Does a reverted subcall roll the change back?
3. Kill test 3Can you point at the object in a client: RFC, URI, EVM?
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

09 Lexicon

Terms, opened into the record

ERC 4804

The public text titled Web3 URL to EVM Call Message Translation.

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.

11 Related

The next papers, as theses

• EIP-4844 · 2022

  Shard Blob Transactions

  A new transaction type carries a blob: a large chunk of data that consensus nodes hold briefly and that the execution layer cannot read byte by byte. Rollups are the intended user. The blob is not cheap forever, and it is not the rollup's proof.

• Plasma · 2017

  Plasma: Scalable Autonomous Smart Contracts

  A 2017 construction for trees of child chains whose state commitments are posted to a parent chain, with exits so a user can leave if the child operator misbehaves. It is an ancestor of later rollup and validium designs, not a synonym for them.

• Arbitrum · 2018

  Arbitrum: Scalable, private smart contracts

  The 2018 USENIX paper on Arbitrum: a verifier that checks a manager's execution of a virtual machine by bisecting disputes, instead of re-executing every instruction. Offchain Labs' later Nitro stack is a descendant, not this paper line for line.