Skip to main content

Getting Started Guide

The API documentation provides Native ETH restaking-related APIs on Eigenlayer. Currently, it offers query and staking services for Native ETH restaking, making it easier for you to integrate our API into your system to perform related restaking operations on Eigenlayer.

EigenLayer API provides the following endpoints:

  1. Create EigenPod Address：Construct a serialized transaction to generate an EigenPod address, which your validator can use as a withdrawal address.
  2. Query EigenPod Address：Allows you to query the generated EigenPod address or check whether an EigenPod address has been created.
  3. Restake：After the validator is activated, call the restake interface to perform the restake operation on EigenLayer.
  4. RestakedBalance：Query the restaked amount.
  5. IsDelegate：Checks whether delegation is still required. If it returns true, delegation is not needed after restaking.
  6. Delegate：Delegate the restaked ETH to a node operator.
  7. Undelegate：undelegation transaction and executes the undelegate operation.
  8. StartCheckpoint：Initiates the checkpoint process to prove the active validator set of the Pod.
  9. VerifyCheckpointProofs：Advances (or completes) the current checkpoint of the Pod.
  10. QueueWithdrawals：The caller queues their deposit shares for withdrawal across strategies.
  11. QueuedWithdrawals-info：Queries the queuedWithdrawals data.
  12. CompleteQueuedWithdrawals：Call this method to complete receiving tokens.
  13. AvsRewards(Get)：Retrieve AVS reward data.
  14. AvsRewards(Post)：Retrieve transaction data for executing the AVS claim.

Steps​

1. Create an EigenPod Address​

Example Request:

curl --request POST \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/podAddress\
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \

Example Response:

{
    "code": 200,
    "message": "Success",
    "result": {
        "to": "0x30770d7E3e71112d7A6b7259542D1f680a70e315",
        "gasLimit": "3511410",
        "data": "0x84d81062",
        "value": "0",
        "chainId": 17000,
        "type": 2,
        "maxFeePerGas": "1000034",
        "maxPriorityFeePerGas": "1000000",
        "serializeTx": "0x02ec82426880830f4240830f4262833594729430770d7e3e71112d7a6b7259542d1f680a70e315808484d81062c0"
    }
}
  • to — The recipient address of this transaction.
  • gasLimit — The maximum gas limit for the block.
  • data — The transaction data.
  • value — The amount sent in this transaction (in Wei).
  • chainId — The chain ID on which this transaction is authorized, as specified by EIP-155.
  • type — The type of this transaction envelope, as defined by EIP-2718.
  • maxFeePerGas — The maximum price per unit of gas (in Wei) that this transaction will pay for both the EIP-1559 block base fee and the priority fee of this transaction.
  • maxPriorityFeePerGas — The price per unit of gas (in Wei) that will be added to the EIP-1559 block base fee. This additional fee incentivizes miners to prioritize this transaction.
  • serializeTx — Serializes the unsigned transaction.

2.Retrieve EigenPod Address​

If the EigenPod address has been created, it will return podAddress. If the EigenPod has not been created, it will return "code": 111130.

Example Request:

curl --request GET \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/podAddress?staker=0x9E8f8190fc5242AA48DB9eA363edE0f5FEd8a15D\
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \

Example Response:

{
  "code": 200,
  "message": "Success",
  "result": {
    "podAddress": "0x36B9F6A2E39082B3986B293cce2488D39a1261e0"
  }
}
  • podAddress— staker的Pod Address。

3. Restake​

The Restake operation verifies the withdrawal credentials. Validator activation may take 16 to 24 hours. You need to check whether the validator is active before proceeding. Please wait for the validator to attain its status and start performing validator duties.You can check the validator status using active_ongoing via Validator—status.

Example Request:

curl --request POST \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/restake \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \
     --data '
{
    "staker": "0x27AABeE07E0dbC8b0de20f42b1a1980871314Ef5",
    "pubkeys": "0x822e4424d2b49dc85f4ac7a5c76866bcdcc8657a9d20be6450df8f47cf21880b4884308afeb70893360806083e782366,0x8612626f9b52a0c21da1b15d9edabfab8731393a66ee3517be8abe3d8586ac7cbf592a522a371535e6fbe3e51e179b55"
}
'

  • staker — Owner of the EigenPod address.
  • pubkeys — Validator’s pubkey, multiple validators separated by commas.

Example Response:

{
    "code": 200,
    "message": "Success",
    "result": {
        "to": "0x30770d7E3e71112d7A6b7259542D1f680a70e315",
        "gasLimit": "3511410",
        "data": "0x3f65cf190000000000000000000000000000000000000000000000000000000067b0a554...",
        "value": "0",
        "chainId": 17000,
        "type": 2,
        "maxFeePerGas": "1000034",
        "maxPriorityFeePerGas": "1000000",
        "serializeTx": "0x02ec82426880830f4240830f4262833594729430770d7e3e71112d7a6b7259542d1f680a70e315808484d81062c0"
    }
}
  • to — The recipient address of this transaction.
  • gasLimit — The maximum gas limit for the block.
  • data — The transaction data.
  • value — The amount sent in this transaction (in Wei).
  • chainId — The chain ID on which this transaction is authorized, as specified by EIP-155.
  • type — The type of this transaction envelope, as defined by EIP-2718.
  • maxFeePerGas — The maximum price per unit of gas (in Wei) that this transaction will pay for both the EIP-1559 block base fee and the priority fee of this transaction.
  • maxPriorityFeePerGas — The price per unit of gas (in Wei) that will be added to the EIP-1559 block base fee. This additional fee incentivizes miners to prioritize this transaction.
  • serializeTx — Serializes the unsigned transaction.

4.Query the Restaked Amount​

When you want to retrieve the amount of ETH currently restaked, you can call this API to query the already restaked ETH amount.

Example Request:

curl --request GET \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/restakedBalance?staker=0x9E8f8190fc5242AA48DB9eA363edE0f5FEd8a15D \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \

Example Response:

{
  "code": 200,
  "message": "Success",
  "result": {
    "restakedBalance": "64007367213000000000"
  }
}
  • restakedBalance—The amount already restaked.

5. IsDelegate​

Check whether the staker has delegated to a node operator. If the staker has already delegated, there is no need to execute delegate after restaking. If not, delegation is required to earn AVS rewards.

Example Request:

curl --request GET \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/isDelegate?staker=0x9E8f8190fc5242AA48DB9eA363edE0f5FEd8a15D \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \

Example Response:

{
  "code": 200,
  "message": "Success",
  "result": {
       "isDelegated": true
  }
}
  • isDelegated— The result of the staker if delegated to a node operator

6. Delegate​

Allows stakers to delegate their assets to an operator. Delegation is all-or-nothing: when a staker delegates to an operator, they delegate their entire assets. A staker can only delegate to one operator at a time.

Example Request:

curl --request POST \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/delegate \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \
     --data '
{
    "operator": "0x3e31908e30b3051dfe056b1d0902b164d78cd8b8"
}
'

Example Response:

{
  "code": 200,
  "message": "successed",
  "result": {
    "to": "0xA44151489861Fe9e3055d95adC98FbD462B948e7",
    "gasLimit": "1244000",
    "data": "0xeea9064b0000000000000000000000003e31908e30b3051dfe056b1d0902b164d78cd8b80...",
    "value": "0",
    "chainId": 17000,
    "type": 2,
    "maxFeePerGas": "4158022",
    "maxPriorityFeePerGas": "4157996",
    "serializeTx": "0x02f8ed82426880833f722c833f72468312fb6094a44151489861fe9e3055d95adc98f..."
  }
}
  • to — The recipient address of this transaction.
  • gasLimit — The maximum gas limit for the block.
  • data — The transaction data.
  • value — The amount sent in this transaction (in Wei).
  • chainId — The chain ID on which this transaction is authorized, as specified by EIP-155.
  • type — The type of this transaction envelope, as defined by EIP-2718.
  • maxFeePerGas — The maximum price per unit of gas (in Wei) that this transaction will pay for both the EIP-1559 block base fee and the priority fee of this transaction.
  • maxPriorityFeePerGas — The price per unit of gas (in Wei) that will be added to the EIP-1559 block base fee. This additional fee incentivizes miners to prioritize this transaction.
  • serializeTx — Serializes the unsigned transaction.

7. Undelegate​

Undelegation immediately sets the staker's delegated shares to 0, decreases the prior operator's delegated shares, and queues withdrawals for all of the staker's deposited assets. For UX reasons, one withdrawal is queued for each strategy in which the staker has deposited assets. Queued withdrawals mimic the behavior of the queueWithdrawals method;The mainnet has a 7-day queuing period. After the waiting period ends, you can delegate to a new operator again. When delegate again, you also need to execute completeQueuedWithdrawals to return the funds to the EigenPod’s restake balance.

Example Request:

curl --request POST \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/undelegate \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \
     --data '
{
    "staker": "0x27AABeE07E0dbC8b0de20f42b1a1980871314Ef5"
}
'
  • staker — Owner of the EigenPod address.

Example Response:

{
  "code": 200,
  "message": "successed",
  "result": {
    "to": "0xA44151489861Fe9e3055d95adC98FbD462B948e7",
    "gasLimit": "4144060",
    "data": "0xda8be8640000000000000000000000000ec6f099d311b3a46acb89fafef99c1b42b5d635",
    "value": "0",
    "chainId": 17000,
    "type": 2,
    "maxFeePerGas": "4158024",
    "maxPriorityFeePerGas": "4157996",
    "serializeTx": "0x02f84c82426880833f722c833f7248833f3bbc94a44151489861fe9e3055d95adc98fbd462b948e780a4da8be8640000000000000000000000000ec6f099d311b3a46acb89fafef99c1b42b5d635c0"
  }
}
  • to — The recipient address of this transaction.
  • gasLimit — The maximum gas limit for the block.
  • data — The transaction data.
  • value — The amount sent in this transaction (in Wei).
  • chainId — The chain ID on which this transaction is authorized, as specified by EIP-155.
  • type — The type of this transaction envelope, as defined by EIP-2718.
  • maxFeePerGas — The maximum price per unit of gas (in Wei) that this transaction will pay for both the EIP-1559 block base fee and the priority fee of this transaction.
  • maxPriorityFeePerGas — The price per unit of gas (in Wei) that will be added to the EIP-1559 block base fee. This additional fee incentivizes miners to prioritize this transaction.
  • serializeTx — Serializes the unsigned transaction.

8.StartCheckpoint​

Checkpoint proofs comprise the bulk of proofs submitted to an EigenPod. Completing a checkpoint means submitting one checkpoint proof for each validator in the pod's active validator set. When a checkpoint is completed, shares are updated accordingly for each of these events. OwnedShares can be withdrawn via the DelegationManager withdrawal queue (see DelegationManager: Undelegating and Withdrawing).

Example Request:

curl --request POST \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/startCheckpoint \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \
     --data '
{
    "staker": "0x27AABeE07E0dbC8b0de20f42b1a1980871314Ef5"
}
'
  • staker — Owner of the EigenPod address.

Example Response:

{
  "code": 200,
  "message": "successed",
  "result": {
    "to": "0xA44151489861Fe9e3055d95adC98FbD462B948e7",
    "gasLimit": "1244000",
    "data": "0xeea9064b0000000000000000000000003e31908e30b3051dfe056b1d0902b164d78cd8b80...",
    "value": "0",
    "chainId": 17000,
    "type": 2,
    "maxFeePerGas": "4158022",
    "maxPriorityFeePerGas": "4157996",
    "serializeTx": "0x02f8ed82426880833f722c833f72468312fb6094a44151489861fe9e3055d95adc98f..."
  }
}
  • to — The recipient address of this transaction.
  • gasLimit — The maximum gas limit for the block.
  • data — The transaction data.
  • value — The amount sent in this transaction (in Wei).
  • chainId — The chain ID on which this transaction is authorized, as specified by EIP-155.
  • type — The type of this transaction envelope, as defined by EIP-2718.
  • maxFeePerGas — The maximum price per unit of gas (in Wei) that this transaction will pay for both the EIP-1559 block base fee and the priority fee of this transaction.
  • maxPriorityFeePerGas — The price per unit of gas (in Wei) that will be added to the EIP-1559 block base fee. This additional fee incentivizes miners to prioritize this transaction.
  • serializeTx — Serializes the unsigned transaction.

9.VerifyCheckpointProofs​

verifyCheckpointProofs is used to make progress on (or complete) the pod's current checkpoint. This method accepts one or more merkle proofs of validators' current balances against a balanceContainerRoot. Additionally, a balanceContainerProof verifies this balanceContainerRoot

Example Request:

curl --request POST \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/verifyCheckpointProofs \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \
     --data '
{
    "staker": "0x27AABeE07E0dbC8b0de20f42b1a1980871314Ef5"
}
'
  • staker —Owner of the EigenPod address.

Example Response:

{
  "code": 200,
  "message": "successed",
  "result": {
    "to": "0xA44151489861Fe9e3055d95adC98FbD462B948e7",
    "gasLimit": "1244000",
    "data": "0xeea9064b0000000000000000000000003e31908e30b3051dfe056b1d0902b164d78cd8b80...",
    "value": "0",
    "chainId": 17000,
    "type": 2,
    "maxFeePerGas": "4158022",
    "maxPriorityFeePerGas": "4157996",
    "serializeTx": "0x02f8ed82426880833f722c833f72468312fb6094a44151489861fe9e3055d95adc98f..."
  }
}
  • to — The recipient address of this transaction.
  • gasLimit — The maximum gas limit for the block.
  • data — The transaction data.
  • value — The amount sent in this transaction (in Wei).
  • chainId — The chain ID on which this transaction is authorized, as specified by EIP-155.
  • type — The type of this transaction envelope, as defined by EIP-2718.
  • maxFeePerGas — The maximum price per unit of gas (in Wei) that this transaction will pay for both the EIP-1559 block base fee and the priority fee of this transaction.
  • maxPriorityFeePerGas — The price per unit of gas (in Wei) that will be added to the EIP-1559 block base fee. This additional fee incentivizes miners to prioritize this transaction.
  • serializeTx — Serializes the unsigned transaction.

10.QueueWithdrawals​

Allows the caller to queue their deposit shares for withdrawal across any strategy. Withdrawals can be completed after MIN_WITHDRAWAL_DELAY_BLOCKS, by calling completeQueuedWithdrawal. This method accepts deposit shares as input - however, the amounts received upon completion may be lower if the staker has experienced slashing.The withdrawal amount entered cannot exceed the amount of withdrawableRestakedExecutionLayerGwei.

Example Request:

curl --request POST \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/queueWithdrawals \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \
     --data '
{
    "staker": "0x27AABeE07E0dbC8b0de20f42b1a1980871314Ef5",
    "amount": 30000000000000000000,
}
'
  • staker — Owner of the EigenPod address.
  • amount — amount of queueWithdrawal.

Example Response:

{
  "code": 200,
  "message": "successed",
  "result": {
    "to": "0xA44151489861Fe9e3055d95adC98FbD462B948e7",
    "gasLimit": "1244000",
    "data": "0xeea9064b0000000000000000000000003e31908e30b3051dfe056b1d0902b164d78cd8b80...",
    "value": "0",
    "chainId": 17000,
    "type": 2,
    "maxFeePerGas": "4158022",
    "maxPriorityFeePerGas": "4157996",
    "serializeTx": "0x02f8ed82426880833f722c833f72468312fb6094a44151489861fe9e3055d95adc98f..."
  }
}
  • to — The recipient address of this transaction.
  • gasLimit — The maximum gas limit for the block.
  • data — The transaction data.
  • value — The amount sent in this transaction (in Wei).
  • chainId — The chain ID on which this transaction is authorized, as specified by EIP-155.
  • type — The type of this transaction envelope, as defined by EIP-2718.
  • maxFeePerGas — The maximum price per unit of gas (in Wei) that this transaction will pay for both the EIP-1559 block base fee and the priority fee of this transaction.
  • maxPriorityFeePerGas — The price per unit of gas (in Wei) that will be added to the EIP-1559 block base fee. This additional fee incentivizes miners to prioritize this transaction.
  • serializeTx — Serializes the unsigned transaction.

11.QueuedWithdrawalsInfo​

Query the data list of executed queueWithdrawals. The undelegate or queuedWithdrawals data can be found through this interface.

Example Request:

curl --request GET \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/queuedWithdrawalsInfo?staker=0x9E8f8190fc5242AA48DB9eA363edE0f5FEd8a15D\
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \
  • staker — Owner of the EigenPod address.
  • queueWithdrawalsTxs — Transaction hash that have entered the withdrawal queue but have not yet completed the final withdrawal. If there are multiple QueueWithdrawals operations, the transaction hash are separated by commas.

Example Response:

{
    "code": 200,
    "message": "Success",
    "result": {
        "restakedBalance": "32001802595000000000",
        "podBalance": "2802595000000000",
        "withdrawableRestakedExecutionLayerGwei": "2802595",
        "avaiableToQueue": "1802595000000000",
        "withdrawQueue": "1000000000000000",
        "avaiableToWithdraw": "0",
        "queuedWithdrawals": [
            {
                "queuedNonce": "0",
                "startBlock": "21915538",
                "shares": "1000000000000000",
                "delaySeconds": 355344
            }
        ]
    }
}
  • restakedBalance — Amount currently being restaked
  • podBalance — Balance of the pod address
  • withdrawableRestakedExecutionLayerGwei — Withdrawable amount verified by checkpoint,the unit of this value is Gwei.
  • avaiableToQueue — Amount available to enter the withdrawal queue
  • withdrawQueue — Amount locked in the withdrawal period
  • avaiableToWithdraw — Amount unlocked and available for final withdrawal
  • queuedWithdrawals — List data of the withdrawal queue
  • queuedNonce — nonce of queuedWithdrawal.
  • startBlock— startBlock of queuedWithdrawal.
  • shares— amount of queuedWithdrawal.
  • delaySeconds—The remaining withdrawal time in the queuedWithdrawal queue, in seconds. When it reaches 0, the completeQueuedWithdrawals operation can be performed.

12. CompleteQueuedWithdrawals​

After MIN_WITHDRAWAL_DELAY_BLOCKS, the staker can complete the withdrawal or restake the shares again by calling the CompleteQueuedWithdrawals method. The staker can choose to receive tokens or shares based on the parameter values in thequeueWithdrawalsTx logs.

Example Request:

curl --request POST \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/completeQueuedWithdrawals \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \
     --data '
{
    "staker": "0x27AABeE07E0dbC8b0de20f42b1a1980871314Ef5",
    "queueWithdrawalsTx": "0x9944c374d311f7d80db6a3bdf373d4a98b3a014c9cd5bb607564661618285987"
}
'
  • staker — Owner of the EigenPod address.
  • queueWithdrawalsTx - The transaction hash of queueWithdrawals, ensuring that the queueWithdrawals has been successfully confirmed on the blockchain and the queue delay has ended.

Example Response:

{
  "code": 200,
  "message": "successed",
  "result": {
    "to": "0xA44151489861Fe9e3055d95adC98FbD462B948e7",
    "gasLimit": "4144060",
    "data": "0x9435bb43000000000000000000000000000000000000000000000000000000000000...",
    "value": "0",
    "chainId": 17000,
    "type": 2,
    "maxFeePerGas": "4158024",
    "maxPriorityFeePerGas": "4157996",
    "serializeTx": "0x02f84c82426880833f722c833f7248833f3bbc94a44151489861fe9e3055d95adc98fbd462b948e780a4da8be8640000000000000000000000000ec6f099d311b3a46acb89fafef99c1b42b5d635c0"
  }
}
  • to — The recipient address of this transaction.
  • gasLimit — The maximum gas limit for the block.
  • data — The transaction data.
  • value — The amount sent in this transaction (in Wei).
  • chainId — The chain ID on which this transaction is authorized, as specified by EIP-155.
  • type — The type of this transaction envelope, as defined by EIP-2718.
  • maxFeePerGas — The maximum price per unit of gas (in Wei) that this transaction will pay for both the EIP-1559 block base fee and the priority fee of this transaction.
  • maxPriorityFeePerGas — The price per unit of gas (in Wei) that will be added to the EIP-1559 block base fee. This additional fee incentivizes miners to prioritize this transaction.
  • serializeTx — Serializes the unsigned transaction.

13.AvsRewards(Get)​

Query the reward data that the staker can claim. Currently, Eigen rewards are distributed once per week, so it is recommended to query at intervals greater than 7 days.

Example Request:

curl --request GET \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/avsRewards?staker=0x9E8f8190fc5242AA48DB9eA363edE0f5FEd8a15D \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json'

Example Response:

{
  "code": 200,
  "message": "successed",
  "result": {
    "rewards": [
        {
        "token": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2",
        "symbol": "WETH",
        "earned": "1548959716822977",
        "active": "1548959716822977",
        "claimed": "0",
        "claimable": "1548959716822977"
        },
        {
        "token": "0xec53bf9167f50cdeb3ae105f56099aaab9061f83",
        "symbol": "EIGEN",
        "earned": "983006337426751957841",
        "active": "983006337426751957841",
        "claimed": "782701837421108939187",
        "claimable": "200304500005643018654"
        }
    ]
  }
}
  • token — The token address of the AVS reward.
  • symbol — The token symbol.
  • earned — The amount of rewards earned.
  • claimed — The amount already claimed.
  • claimable — The amount currently available for claiming.

14.AvsRewards(Post)​

If the query AvsRewards(Get) shows that the staker has claimable reward data, you can call this API to generate the claim AVS reward data and proceed with the claim operation. Rewards are distributed once per week, so it is recommended to call this API at intervals greater than 7 days.

Example Request:

curl --request POST \
     --url http://api-test.ssv.ebunker.io/api/v1/eth/restake/eigenlayer/avsRewards \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json' \
     --data '
{
    "staker": "0x27AABeE07E0dbC8b0de20f42b1a1980871314Ef5",
    "tokenAddresses": "0x3b78576f7d6837500ba3de27a60c7f594934027e,0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2"
}
'
  • staker — Owner of the EigenPod address.
  • tokenAddresses — The address of the AVS reward token, multiple token addresses separated by commas, can be retrieved from the AvsRewards(GET) API.

Example Response:

{
  "code": 200,
  "message": "successed",
  "result": {
    "to": "0xA44151489861Fe9e3055d95adC98FbD462B948e7",
    "gasLimit": "1244000",
    "data": "0xeea9064b0000000000000000000000003e31908e30b3051dfe056b1d0902b164d78cd8b80...",
    "value": "0",
    "chainId": 17000,
    "type": 2,
    "maxFeePerGas": "4158022",
    "maxPriorityFeePerGas": "4157996",
    "serializeTx": "0x02f8ed82426880833f722c833f72468312fb6094a44151489861fe9e3055d95adc98f..."
  }
}
  • to — The recipient address of this transaction.
  • gasLimit — The maximum gas limit for the block.
  • data — The transaction data.
  • value — The amount sent in this transaction (in Wei).
  • chainId — The chain ID on which this transaction is authorized, as specified by EIP-155.
  • type — The type of this transaction envelope, as defined by EIP-2718.
  • maxFeePerGas — The maximum price per unit of gas (in Wei) that this transaction will pay for both the EIP-1559 block base fee and the priority fee of this transaction.
  • maxPriorityFeePerGas — The price per unit of gas (in Wei) that will be added to the EIP-1559 block base fee. This additional fee incentivizes miners to prioritize this transaction.
  • serializeTx — Serializes the unsigned transaction.