POST
/
2fc1de7f08c0465f6a28e3c355e0cb14
eth_createAccessList
curl --request POST \
  --url https://base-mainnet.core.chainstack.com/2fc1de7f08c0465f6a28e3c355e0cb14 \
  --header 'Content-Type: application/json' \
  --data '{
  "jsonrpc": "2.0",
  "method": "eth_createAccessList",
  "id": 1,
  "params": [
    {
      "from": "0xaeA8F8f781326bfE6A7683C2BD48Dd6AA4d3Ba63",
      "data": "0x608060806080608155"
    },
    "pending"
  ]
}'
{
  "jsonrpc": "<string>",
  "id": 123,
  "result": {
    "accessList": [
      {
        "address": "<string>",
        "storageKeys": [
          "<string>"
        ]
      }
    ],
    "gasUsed": "<string>"
  }
}

Base API method eth_createAccessList generates an access list for a transaction based on specific default values. An access list includes addresses and storage keys the transaction intends to access, facilitating more efficient gas usage.

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • transactionObject — an object containing transaction parameters with default values:
    • from — the address of the sender.
    • data — the data being sent with the transaction.
  • blockParameter — specifies the blockchain state to use for generating the access list, with a default value of "pending".

​
Response

  • result — an object containing:
    • accessList — the generated access list, detailing addresses and storage keys the transaction will access.
    • gasUsed — the estimated gas used to execute the transaction with the generated access list.

​
Use case

The eth_createAccessList method is crucial for:

  • Preparing transactions that optimize gas usage by explicitly stating which addresses and storage keys will be accessed.
  • Developers aiming to reduce transaction costs and improve efficiency on the Base network.
  • Transactions that comply with EIP-2930, which introduces access lists as a transaction type to specify state access.

This method provides a practical approach to optimizing transaction execution and gas usage on the Base blockchain by pre-determining the access list.

Body

application/json

Response

200 - application/json

The generated access list and gas used

The response is of type object.

POST
/
2fc1de7f08c0465f6a28e3c355e0cb14
eth_createAccessList
curl --request POST \
  --url https://base-mainnet.core.chainstack.com/2fc1de7f08c0465f6a28e3c355e0cb14 \
  --header 'Content-Type: application/json' \
  --data '{
  "jsonrpc": "2.0",
  "method": "eth_createAccessList",
  "id": 1,
  "params": [
    {
      "from": "0xaeA8F8f781326bfE6A7683C2BD48Dd6AA4d3Ba63",
      "data": "0x608060806080608155"
    },
    "pending"
  ]
}'
{
  "jsonrpc": "<string>",
  "id": 123,
  "result": {
    "accessList": [
      {
        "address": "<string>",
        "storageKeys": [
          "<string>"
        ]
      }
    ],
    "gasUsed": "<string>"
  }
}

Base API method eth_createAccessList generates an access list for a transaction based on specific default values. An access list includes addresses and storage keys the transaction intends to access, facilitating more efficient gas usage.

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • transactionObject — an object containing transaction parameters with default values:
    • from — the address of the sender.
    • data — the data being sent with the transaction.
  • blockParameter — specifies the blockchain state to use for generating the access list, with a default value of "pending".

​
Response

  • result — an object containing:
    • accessList — the generated access list, detailing addresses and storage keys the transaction will access.
    • gasUsed — the estimated gas used to execute the transaction with the generated access list.

​
Use case

The eth_createAccessList method is crucial for:

  • Preparing transactions that optimize gas usage by explicitly stating which addresses and storage keys will be accessed.
  • Developers aiming to reduce transaction costs and improve efficiency on the Base network.
  • Transactions that comply with EIP-2930, which introduces access lists as a transaction type to specify state access.

This method provides a practical approach to optimizing transaction execution and gas usage on the Base blockchain by pre-determining the access list.

Body

application/json

Response

200 - application/json

The generated access list and gas used

The response is of type object.