# Send a transaction (eth_sendTransaction)

> A request to create, sign and send a transaction. A plain transfer moves value once it is included; the same request type also carries contract calls, including approvals.

- Request: `eth_sendTransaction`
- Standard: EIP-1474 (JSON-RPC)
- Track: Request types
- Checked against sources: 2026-11-04
- Review status: drafted with AI assistance, awaiting human review
- Canonical page: https://walletpermissions.com/learn/requests/send-transaction

Education only. This does not assess any real request, wallet or app, and is not advice to sign or not sign. Every app, token and address in the practice card is fictional.

## What to read in the prompt

- `to`: ethereum.org explains that if it is an externally-owned account “the transaction will transfer value. If a contract account, the transaction will execute the contract code.”
- `value`: the amount of ETH sent.
- `data`: empty for a plain transfer. If it is not empty, it is a contract call. Read the decoded function name.
- The network.

## What it lets the other party do

- EIP-1474 describes the method as: “Creates, signs, and sends a new transaction to the network.”
- With `data`, your account calls a contract function. That function can be `approve` or `setApprovalForAll`, so a “transaction” can be a permission.

## What it does not do

- A plain value transfer does not create any allowance for later.
- It is not reversible once settled. ethereum.org: once a block is finalized “it could only ever be changed by a network level attack that would cost many billions of dollars.”

## How long it lasts

- A transfer is a single event. A contract call can leave lasting state, such as an allowance.

## How to undo it

- A completed transfer has no undo. Setting an allowance to 0 does not bring back tokens that moved.
- If the call was an approval, remove it as described on the approval pages, and check with Revoke.cash or Etherscan’s token approval checker.

## A pattern to recognise

- A transaction with a value of 0 that looks like it “does nothing” but whose data is an approval. ethereum.org calls opaque data a “blind signing” problem.

## Practice question (fictional)

Fictional Orchard asks you to confirm a transaction.

| Field | Value |
| --- | --- |
| Request type | Transaction: eth_sendTransaction |
| to | LEAF token contract (fictional) |
| value | 0 ETH |
| data (decoded) | approve(Orchard Router, maximum) |

**Question:** Because the value is 0, does this transaction leave your tokens untouched in every way?

**Answer:** No. Value is the ETH sent. The data is an `approve` call that gives Orchard Router an unlimited LEAF allowance.

## Check your real account elsewhere

This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements):

- [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks
- [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet

## Sources

- [EIP-1474: Remote procedure call specification (eth_sendTransaction)](https://eips.ethereum.org/EIPS/eip-1474). Ethereum EIPs. Stagnant; created 2018-10-02. Checked 2026-11-04.
- [Transactions (developer docs)](https://ethereum.org/developers/docs/transactions/). ethereum.org. Page as published on the check date. Checked 2026-11-04.
- [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04.
