eth_createAccessList

Creates an EIP-2930 access list that you can include in a transaction.

Use this method to optimize your smart contract interactions. Access lists are a part of Ethereum's EIP-2930, which aims to improve the network's scalability and reduce gas costs by specifying an explicit list of addresses and storage keys that a transaction intends to access.

Parameters

  • Transaction call object: [Required]

    • from: 20 bytes. The address of the sender.

    • to: 20 bytes. Address the transaction is directed to.

    • gas: Hexadecimal value of the gas provided for the transaction execution.

    • gasPrice: Hexadecimal value gas price (in wei) provided by the sender. The default is 0. Used only in non-EIP-1559 transactions.

    • maxPriorityFeePerGas: Maximum fee (in wei) the sender is willing to pay per gas above the base fee. See EIP-1559 transactions. If used, must specify maxFeePerGas.

    • maxFeePerGas: Maximum total fee (base fee + priority fee, in wei), the sender is willing to pay per gas. See EIP-1559 transactions. If used, must specify maxPriorityFeePerGas.

    • value: Hexadecimal of the value transferred, in wei.

    • data: Hash of the method signature and encoded parameters. See Ethereum contract ABI specification.

  • block parameter: A string representing a block number, block hash, or one of the string tags latest, earliest, pending, safe, or finalized. See the default block parameter.

Returns

Access list object with the following fields:

  • accessList: A list of objects with the following fields:

    • address: Addresses to be accessed by the transaction.

    • storageKeys: Storage keys to be accessed by the transaction.

  • gasUsed: A hexadecimal string representing the approximate gas cost for the transaction if the access list is included.

Example

Request

curl https://rpc.testnet.tryradi.us/<YOUR-RPC-ENDPOINT> \
  -X POST \
  -H "Content-Type: application/json" \
  -d '
{
  "jsonrpc": "2.0",
  "method": "eth_createAccessList",
  "params": [
    {
      "from": "0xcAE4D474A43B186606bB836F463d4b4072B7fBe3",
      "data": "0x406080806080606174"
    },
    "pending"
  ],
  "id": 1
}
'

Response

{
  "jsonrpc": "2.0",
  "error": {
    "code": -32601,
    "message": "Method not found"
  },
  "id": 1
}

Last updated

Was this helpful?