EIP-7702

https://eip7702.io/
Admin
EIP-7702 introduces a new transaction type that allows Externally Owned Accounts (EOAs) to set their...
Tokens:1,644
Snippets:6
Trust Score:6.8
Update:1 year ago
Show doc for...
Tokens:
Raw
### EIP-7702 Transaction Batching with TypeScript

Source: https://eip7702.io/examples

Executes batched transactions after the EOA has been delegated to a smart account implementation. This example uses `executeBatch` to send multiple calls. Requires `accountAbi`, `account`, and `walletClient` from a client setup.

```typescript
import { zeroAddress } from "viem";

import accountAbi from "./abi.js";
import { account, walletClient } from "./client.js";

const hash = await walletClient.writeContract ({
	abi: accountAbi,
	address: account.address,
	functionName: "executeBatch",
	args: [
		[
			{
			target: zeroAddress,
			value: 1n,
			data: "0x",
			},
			{
			target: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
			value: 0n,
			data: "0xdeadbeef",
			},
		],
	],
});
console.log(`Transaction hash ${hash}`);
```

--------------------------------

### EIP-7702 Basic Authorization with TypeScript

Source: https://eip7702.io/examples

Sets the Externally Owned Account (EOA) code to the `Simple7702Account` implementation. It generates an authorization signature and sends a transaction to delegate the EOA. Requires `walletClient` from a client setup.

```typescript
import { walletClient } from "./client.js";

const accountImplementation = "0x4Cd241E8d1510e30b2076397afc7508Ae59C66c9";

const authorization = await walletClient.signAuthorization({
	contractAddress: accountImplementation,
	executor: "self",
});

const hash = await walletClient.sendTransaction ({
	authorizationList: [authorization],
	data: "0x",
	to: walletClient.account.address,
});
console.log(`Delegated at tx ${hash}`);
```

--------------------------------

### EIP-7702 Sending User Operation with TypeScript

Source: https://eip7702.io/examples

Signs and sends a User Operation using the ERC-4337 flow, assuming the account is initialized and the EOA is the owner. This can also sponsor transactions via a paymaster. Requires `smartAccount` and `bundlerClient` from client setup.

```typescript
import { zeroAddress } from "viem";

import { smartAccount } from "./account.js";
import { bundlerClient } from "./client.js";

const userOpHash = await bundlerClient.sendUserOperation ({
	account: smartAccount,
	calls: [
		{
			to: zeroAddress,
			value: 1n,
		},
		{
			to: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
			data: "0xdeadbeef",
		},
	],
});
console.log(`User operation sent ${userOpHash}`);
```

--------------------------------

### EIP-7702 Authorization Verification Logic

Source: https://eip7702.io/index

Outlines the step-by-step verification process for each authorization tuple within an EIP-7702 transaction. This includes chain ID validation, nonce checks, cryptographic signature recovery, and address code verification.

```text
1. Verify the chain id is either 0 or the chain’s current ID.
2. Verify the `nonce` is less than `2**64 - 1`.
3. `authority = ecrecover(keccak(0x05 || rlp([chain_id, address, nonce])), y_parity, r, s)`
   * `s` value must be less or equal than `secp256k1n/2`, as specified in EIP-2.
4. Add `authority` to `accessed_addresses` (as defined in EIP-2929.)
5. Verify the code of `authority` is either empty or already delegated.
6. Verify the nonce of `authority` is equal to `nonce`. In case `authority` does not exist in the trie, verify that `nonce` is equal to `0`.
7. Add `PER_EMPTY_ACCOUNT_COST - PER_AUTH_BASE_COST` gas to the global refund counter if `authority` exists in the trie.
8. Set the code of `authority` to be `0xef0100 || address`.
   * Special case: If `address` is `0x0000000000000000000000000000000000000000`, clear code and reset hash to `0xc5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470`.
9. Increase the nonce of `authority` by one.
```

--------------------------------

### EIP-7702 Set Code Transaction

Source: https://eip7702.io/index

Details the structure and behavior of the new 'set code transaction' introduced by EIP-7702, including its transaction type, payload, and execution logic for authorization lists.

```APIDOC
## POST /eip-7702/set-code

### Description
This endpoint represents the new 'set code transaction' defined in EIP-7702. It allows an EOA to authorize delegation of its code to an existing smart contract by submitting a signed transaction.

### Method
POST

### Endpoint
`/eip-7702/set-code`

### Parameters
#### Path Parameters
None

#### Query Parameters
None

#### Request Body
- **transaction_payload** (string) - RLP serialized: `[chain_id, nonce, max_priority_fee_per_gas, max_fee_per_gas, gas_limit, destination, value, data, access_list, authorization_list, signature_y_parity, signature_r, signature_s]`
  - **authorization_list** (array) - A list of tuples: `[[chain_id, address, nonce, y_parity, r, s], ...]`
    - **chain_id** (uint256) - The chain ID for the authorization.
    - **address** (address) - The address to which the EOA's code is delegated.
    - **nonce** (uint64) - The nonce for the authorization.
    - **y_parity** (uint8) - The y-parity of the signature.
    - **r** (uint256) - The r component of the signature.
    - **s** (uint256) - The s component of the signature.

### Request Example
```json
{
  "transaction_payload": "0xf8a388..."
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates success or failure of the transaction.
- **cumulative_transaction_gas_used** (uint256) - The cumulative gas used by the transaction.
- **logs_bloom** (bytes) - The bloom filter for logs.
- **logs** (array) - A list of emitted logs.

#### Response Example
```json
{
  "status": "success",
  "cumulative_transaction_gas_used": 100000,
  "logs_bloom": "0x...",
  "logs": []
}
```

### Error Handling
- **400 Bad Request**: Invalid transaction payload or signature.
- **500 Internal Server Error**: An unexpected error occurred during transaction processing.
```

--------------------------------

### EIP-7702 Transaction Payload Structure

Source: https://eip7702.io/index

Defines the RLP serialization format for the EIP-7702 'set code transaction' and its authorization list. This structure dictates how transaction details and authorization tuples are encoded for network transmission.

```text
rlp([chain_id, nonce, max_priority_fee_per_gas, max_fee_per_gas, gas_limit, destination, value, data, access_list, authorization_list, signature_y_parity, signature_r, signature_s])

authorization_list = [[chain_id, address, nonce, y_parity, r, s], ...]
```
Tokens:
Raw