Withdrawal

The withdrawal process in the Celestia network using the Staking API can be done in a few steps:

1. Create an unstake transaction.
2. Sign and send the transaction to the network.

1. Create Unstake Transaction

1. Send a POST request to /api/v1/celestia/{network}/staking/unstake.

   Example request (for celestia-mainnet-beta network):

   cURL

   curl --request POST \
        --url https://api-test.p2p.org/api/v1/celestia/celestia-mainnet-beta/staking/unstake \
        --header 'accept: application/json' \
        --header 'authorization: Bearer <token>' \
        --header 'content-type: application/json' \
        --data '
        {
        "delegatorAddress": "celestia1yknsyf9ws4ugtv3r9g43kwqkne4zmrupae4xb2",
        "memo": "This is your memo message",
        "amount": 0.0001
        }'
   

   • stashAccountAddress — delegator account address which keeps tokens.
   • memo — arbitrary text data to add to the transactions.
   • amount — amount of tokens to unstake in TIA.

   Example response:

   JSON

   {
     "error": null,
     "result": {
       "amount": 0.0001,
       "currency": "tia",
       "validatorAddress": "celestiavaloper1r4kqtye4dzacmrwnh6f057p50pdjm8g59tlhhg",
       "delegatorAddress": "celestia1yknsyf9ws4ugtv3r9g43kwqkne4zmrupae4xb2",
       "transactionData": {
         "messages": [
           {
             "typeUrl": "/cosmos.staking.v1beta1.MsgUndelegate",
             "value": {
               "delegatorAddress": "celestia1yknsyf9ws4ugtv3r9g43kwqkne4zmrupae4xb2",
               "validatorAddress": "celestiavaloper1r4kqtye4dzacmrwnh6f057p50pdjm8g59tlhhg",
               "amount": {
                 "denom": "utia",
                 "amount": "100"
               }
             }
           }
         ],
         "fee": {
           "amount": [
             {
               "amount": "16384",
               "denom": "utia"
             }
           ],
           "gas": "655324"
         },
         "memo": "This is your memo message",
         "encodedBody": "0a9c010a252f636f736d6f732e7374616b696e672e763162657461312e4d7367556e64656c656761746512730a2d636f736d6f733179397765666d6c706d30646a6b74387373656576656b653068747466756b67326136306730721234636f736d6f7376616c6f7065723133326a757a6b3067646d77757876783470687567376d33796d796174786c68393733346734771a0c0a057561746f6d1203313030120b546865206d657373616765",
         "encodedAuthInfo": "0a500a460a1f2f636f736d6f732e63727970746f2e736563703235366b312e5075624b657912230a2103b0c7ac278e1941ac0b65d6bd45d541cae58aa584058fbbd822311b8718708c0e12040a020801180212140a0e0a057561746f6d1205313633383410dcff27"
       },
       "createdAt": "2023-11-03T10:10:05.407Z"
     }
   }
   

• amount — amount of tokens to stake.
• currency — currency of tokens:
  • tia — TIA, Celestia native staking token.
  • utia — 1 TIA = 10^-6 uTIA,
  • mtia — 1 TIA = 10^-3 mTIA.
• validatorAddress — validator address to which tokens are delegated.
• stashAccountAddress — delegator stash account address which keeps tokens.
• rewardDestinationAddress — reward destination account address.
• createdAt — timestamp of the transaction in the ISO 8601 format.

transactionData is the list of data fields to be used to construct the staking transactions:

• messages:
  • typeUrl — Celestia network operation type.
  • delegatorAddress — delegator address.
  • validatorAddress — validator address.
  • amount — amount of tokens to unstake.
  • denom — currency of tokens.
• fee — fee charged for the transaction.
  • amount — amount of tokens.
  • denom — currency of tokens: tia, utia, or mtia.
  • gas — amount of gas spent for the transaction.
• memo — arbitrary text data to add to the transactions.
• encodedBody — processable transaction data encoded in the hexadecimal format.
• encodedAuthInfo — authorization data, including fee, encoded in the hexadecimal format.

2. Sign and Send Transaction

Use transactionData to sign and send the signed transaction to the Celestia network.

To check the transaction status, send a GET request to /api/v1/celestia/{network}/transaction/status/{transactionHash}.

Example request (for celestia-mainnet-beta network):

curl --request GET \
     --url https://api-test.p2p.org/api/v1/celestia/celestia-mainnet-beta/transaction/status/ADD7B2791E1959075D1836D4BCC71ED256CCD724459F9BD8862D85E205075D47 \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <token>' \
     --header 'content-type: application/json'

• transactionHash — hash of the transaction.

Example response:

{
    "error": null,
    "result": {
        "status": "success",
        "blockId": 18575267,
        "fee": 0.005952,
        "gas": {
            "used": 202947,
            "wanted": 238047
        },
        "transactionHash": "ADD7B2791E1959075D1836D4BCC71ED256CCD724459F9BD8862D85E205075D47"
    }
}

• status — transaction status: success, failed.
• blockId — unique identifier of the block in which the transaction has been included.
• fee — total fee in TIA charged for processing the transaction.
• gas — computational effort required to execute the transaction, measured in gas units.
  • used — amount of gas spent for the transaction.
  • wanted — maximum gas limit that the transaction initiator was willing to consume for the transaction.
• transactionHash — hash of the transaction.

What's Next?

• Staking API reference.