Tendermint Token Activation Task Status
API-v2task::enable_tendermint_token::status
After running the task::enable_tendermint_token::init method, you can query the status of activation to check its progress. The response will return the following:
- Result of the task (success or error)
- Progress status (what state the task is in)
- Required user action (what user should do before the task can continue)
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| task_id | integer | ✓ | - | The identifying number returned when initiating the initialisation process. |
| forget_if_finished | boolean | ✗ | true | If false, will return the final response for completed tasks. |
Tendermint Token Activation Status
POST
task::enable_tendermint_token::status{
"userpass": "RPC_UserP@SSW0RD",
"mmrpc": "2.0",
"method": "task::enable_tendermint_token::status",
"params": {
"task_id": 5,
"forget_if_finished": false
}
}
| Parameter | Type | Description |
|---|---|---|
| status | TaskActivationStatusEnum | A short indication of how the enabling is progressing. |
| details | object | Depending on the state of enabling progress, this will contain different information as shown in the responses below. |
Once complete, status will be Ok, and the details object will have the following structure:
| Parameter | Type | Description |
|---|---|---|
| current_block | integer | Block height of the Tendermint chain |
| platform_coin | string | Platform coin used to support the token (e.g., ATOM, KAVA). |
| ticker | string | Ticker of the Tendermint token being activated. |
| token_ibc_denom | string | Full IBC denomination or contract address for the token. |
| wallet_balance | object | A standard WalletBalanceInfo object. Note: the structure may vary based on the get_balances parameter value in the activation request. |
| Parameter | Type | Description |
|---|---|---|
| status | string | A short indication of how the requested process is progressing. |
| details.result | object | Depending on the state of process progress, this will contain different information as detailed in the items below. |
| .error | string | The ticker of the token being activated |
| .error_path | string | Used for debugging. A reference to the function in code base which returned the error |
| .error_trace | string | Used for debugging. A trace of lines of code which led to the returned error |
| .error_type | string | An enumerated error identifier to indicate the category of error |
| .error_data | string | Additional context for the error type |
Possible Error Cases:
TaskTimedOut– Timed out waiting for token activation, connecting to the device, or for user confirmation on the hardware wallet.CoinCreationError– Error during platform coin activation or RPC communication.HwError– This is the most important error type. Unlike other error types,HwErrorrequires the GUI / User to check the details inerror_datafield to know which action is required. View the HwError error type details for more info.