# Reading Ethereum wallet requests: connection, signing and calls

A wallet request can expose an account, sign a message or authorize a transaction; these are different actions. Contract interfaces help decode function names and arguments, while typed-message formats add context to signatures. A request with no immediate gas fee can still authorize a consequential action later.

Evidence: [EIP-1193: Ethereum Provider JavaScript API](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-1193.md); [EIP-712: Typed structured data hashing and signing](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-712.md); [Interacting with smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/interacting/index.md)

Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-wallet-requests/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T18:16:35.976Z

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Connection:** Provider communication and account exposure are distinct from a transfer ([EIP-1193: Ethereum Provider JavaScript API](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-1193.md))
- **ABI:** Describes contract functions, arguments and events ([Interacting with smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/interacting/index.md))
- **Typed signature:** Provides structure and domain context, not automatic safety ([EIP-712: Typed structured data hashing and signing](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-712.md))

## Connection, signing and submission establish different things

Connecting a wallet lets an application request interaction with an account; it is not itself an ERC-20 spending approval. A signature can authorize a message, order, permit or transaction, depending on what is signed.

Signing is also different from submitting. Someone can hold a valid permit and submit it later under its nonce and deadline rules. A request with no immediate gas charge can therefore create consequential authority. Read the verifying contract, chain, spender, amount and validity conditions before treating it as a login.

Evidence: [Ethereum transactions](https://ethereum.org/en/developers/docs/transactions/); [Typed structured data hashing and signing](https://eips.ethereum.org/EIPS/eip-712); [Permit Extension for EIP-20 Signed Approvals](https://eips.ethereum.org/EIPS/eip-2612); [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20); [EIP-1193: Ethereum Provider JavaScript API](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-1193.md)

## Example: approving a spender is different from paying a recipient

Suppose a decoded request says approve a spender for 100 token units. That changes the permitted spending allowance if executed; it is not the same instruction as transfer 100 units to a recipient.

The ABI is the interface description used to turn bytes into readable function names and arguments. The actual token contract, spender, amount and chain still matter. A familiar function name does not authenticate the destination.

Evidence: [Interacting with smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/interacting/index.md); [ERC-20: Token Standard](https://raw.githubusercontent.com/ethereum/ERCs/583335b7912e51b1ea515bb662532dd29b27e786/ERCS/erc-20.md)

## A structured message helps show what is being signed

EIP-712 defines typed structured data and domain separation. Fields can include an application name, version, chain and verifying contract. These give software a way to display more context than an opaque byte string.

The standard explicitly does not provide application replay protection by itself. An application still needs appropriate nonces, deadlines or other rules, and the wallet’s presentation cannot establish that the verifier implements them correctly.

Evidence: [EIP-712: Typed structured data hashing and signing](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-712.md); [EIP-1193: Ethereum Provider JavaScript API](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-1193.md)

## A preview answers a narrower question than a guarantee

A simulation estimates execution against selected state. A later transaction may encounter a different price, balance or ordering. Treat the preview as evidence about those assumptions rather than a promise of the final outcome.

Account delegation deserves special attention: EIP-7702 authorization can grant persistent execution capabilities. It should not be confused with a routine login signature or permission to view an account.

Evidence: [Interacting with smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/interacting/index.md); [EIP-7702: Set Code for EOAs](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-7702.md)

## Questions

### Does connecting a wallet move my tokens?

Account exposure alone does not execute a transfer. Additional signatures or transactions can grant authority, so distinguish each request rather than treating every prompt as connection.

Evidence: [EIP-1193: Ethereum Provider JavaScript API](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-1193.md); [ERC-20: Token Standard](https://raw.githubusercontent.com/ethereum/ERCs/583335b7912e51b1ea515bb662532dd29b27e786/ERCS/erc-20.md)

### Is signing a message safe because it costs no gas?

No. A signature can authorize a later action when presented to a contract or service. Its effect depends on the message and the rules that verify it.

Evidence: [EIP-712: Typed structured data hashing and signing](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-712.md)

### Does readable transaction text prove a contract is legitimate?

No. Decoding explains the requested function and arguments. It does not certify the destination contract, its implementation or the site making the request.

Evidence: [Interacting with smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/interacting/index.md); [Introduction to smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/index.md)

## Claims and scope

### ethereum-wallet-requests-quick-answer

A wallet request can expose an account, sign a message or authorize a transaction; these are different actions. Contract interfaces help decode function names and arguments, while typed-message formats add context to signatures. A request with no immediate gas fee can still authorize a consequential action later.

Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null}

### ethereum-wallet-requests-fact-connection

Connection: Provider communication and account exposure are distinct from a transfer

Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null}

### ethereum-wallet-requests-fact-abi

ABI: Describes contract functions, arguments and events

Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null}

### ethereum-wallet-requests-fact-typed-signature

Typed signature: Provides structure and domain context, not automatic safety

Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null}

## Sources

- [EIP-1193: Ethereum Provider JavaScript API](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-1193.md) — Ethereum Improvement Proposals. Defines wallet provider requests, account/chain changes and the boundary between provider communication and wallet permission. Locator: request; events; security considerations; user account exposure. Retrieved: 2026-10-02T14:35:55.037764+00:00.
- [EIP-712: Typed structured data hashing and signing](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-712.md) — Ethereum Improvement Proposals. Defines typed-message structure and domain separation; explicitly does not supply application replay protection. Locator: Abstract; domainSeparator; security considerations. Retrieved: 2026-10-02T14:35:55.017191+00:00.
- [Interacting with smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/interacting/index.md) — ethereum.org contributors. Supports read-only calls, state-changing transactions, ABI decoding and limits of simulation. Locator: Reading; writing; understanding contract ABIs; events and logs; simulating. Retrieved: 2026-10-02T14:35:40.398262+00:00.
- [ERC-20: Token Standard](https://raw.githubusercontent.com/ethereum/ERCs/583335b7912e51b1ea515bb662532dd29b27e786/ERCS/erc-20.md) — Ethereum Request for Comments. Defines fungible token balances, optional display metadata and spending allowance behavior. Locator: Methods: decimals, balanceOf, transfer, approve, transferFrom, allowance. Retrieved: 2026-10-02T14:35:55.037727+00:00.
- [EIP-7702: Set Code for EOAs](https://raw.githubusercontent.com/ethereum/EIPs/ac912ca6a9685590345dd8e5736cda75976d0131/EIPS/eip-7702.md) — Ethereum Improvement Proposals. Defines persistent EOA code delegation, continued transaction origination and the account-wide consequences of delegate code. Locator: Abstract; persistence of code delegation; transaction origination; security considerations. Retrieved: 2026-10-02T14:35:51.249142+00:00.
- [Introduction to smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/index.md) — ethereum.org contributors. Supports contract code/state, deterministic rules, illustrative vending logic, external-data limits and multisignature access. Locator: What is a smart contract; a digital vending machine; limitations; multisig. Retrieved: 2026-10-02T14:35:40.398357+00:00.
- [Ethereum transactions](https://ethereum.org/en/developers/docs/transactions/) — ethereum.org contributors. Signed transaction fields, nonces, propagation, inclusion and transaction types. Locator: The transaction lifecycle; Typed transaction envelope. Retrieved: 2026-10-02T17:03:41.854Z.
- [Typed structured data hashing and signing](https://eips.ethereum.org/EIPS/eip-712) — Ethereum Improvement Proposals. Typed-data encoding and domain fields; replay protection is application-specific. Locator: Specification; Security Considerations. Retrieved: 2026-10-02T17:03:42.239Z.
- [Permit Extension for EIP-20 Signed Approvals](https://eips.ethereum.org/EIPS/eip-2612) — Ethereum Improvement Proposals. Signed token allowances, deadlines, nonces and domain checks. Locator: Specification; Security Considerations. Retrieved: 2026-10-02T17:03:42.295Z.
- [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20) — Ethereum Improvement Proposals. Token supply, displayed units and balance accounting. Locator: totalSupply; balanceOf; transfer; decimals; approve; allowance; transferFrom; Transfer. Retrieved: 2026-10-02T17:03:45.826Z.

## Revision history

- 2026-10-02: First publication after primary-source research and independent automated verification.
- 2026-10-02: Expanded explanation: Connection, signing and submission establish different things. Worked examples are illustrative; source checks and independent verification are recorded separately.

## Cite this entry

Degrees of Satoshi editorial project. “Reading Ethereum wallet requests: connection, signing and calls.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-wallet-requests/