Wallet Call API

The five-minute read

One action, walked through

1. Open EIP 5792 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Defines new JSON-RPC methods which enable apps to ask a wallet to process a batch of onchain write calls and to check on the status of those calls.
3. Name the object that changes: JSON, RPC, API.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing EIP 5792 at the status the text itself states: Final.
• The object that has to change is JSON, RPC, API. A neighbouring document with a similar name is not this one.
• Status in the header is not adoption.

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.

What to check before you use the idea

• What must an implementation of Wallet Call API accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: JSON, RPC, API?

Terms

EIP 5792

The public text titled Wallet Call API.

Final

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.

What the design proposes

• Defines new JSON-RPC methods which enable apps to ask a wallet to process a batch of onchain write calls and to check on the status of those calls.
• Applications can specify that these onchain calls be executed taking advantage of specific capabilities previously expressed by the wallet; an additional, novel wallet RPC is defined to enable apps to query the wallet for those capabilities.
• The current methods used to send transactions from the user wallet and check their status are eth_sendTransaction and eth_getTransactionReceipt.

How the mechanism is specified

• Taken from the specification, the next constraint is: Applications can specify that these onchain calls be executed taking advantage of specific capabilities previously expressed by the wallet; an additional, novel wallet RPC is defined to enable apps to query the wallet for those capabilities.
• Locate JSON, RPC, API in EIP 5792 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

• This document does not set a fee, a valuation, or a security proof.
• Status in the header is not adoption.
• The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use EIP 5792 when a pitch says 'Wallet Call API' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.