task::enable_bch

API-v2task::enable_bch::init

init

BCH and SLP tokens can be activated in a task managed manner using this method.

Arguments

Parameter	Type	Description
ticker	string	Ticker of the platform protocol coin. Options: `BCH` or `tBCH`
bchd_urls	array of strings	A list of BCHD gRPC API server URLs, used for validation of SLP token transactions. It's recommended to add as many servers as possible. The URLs list can be found at https://bchd.fountainhead.cash/.
mode	object	A standard ActivationMode object.
tx_history	boolean	If `true`, spawns a background loop to store the local cache of address(es) transactions. Defaults to `false`.
slp_tokens_requests	array of objects	A list of standard TokensRequest objects.
address_format	object	Optional. Overwrites the address format from coins file, if set. A standard AddressFormat object.
allow_slp_unsafe_conf	boolean	Optional, defaults to `false`. If `true`, allows bchd_urls to be empty. Warning: it is highly unsafe to do so as it may lead to invalid SLP transactions generation and tokens burning.
get_balances	boolean	Optional, defaults to `true`. If `false`, coin and token balances will not be returned in the response, and the response will be returned more quickly.
required_confirmations	integer	Optional, defaults to value in the coins file, or `3` if not set. Confirmations to wait for steps in swap.
requires_notarization	boolean	Optional, defaults to `true`. Has no effect on BCH.
tx_history	boolean	Optional, defaults to `true`. If `true` the Komodo DeFi Framework API will preload transaction history as a background process. Must be set to `true` to use the my_tx_history method
utxo_merge_params	object	A standard UtxoMergeParams object. Used to reduce a wallet's UTXO count in cases where it is causing significantly slower RPC responses.

Response

Parameter	Type	Description
task_id	integer	An identifying number which is used to query task status.

📌 Examples

Activation in Trezor mode

POST

task::enable_bch::init

{
  "userpass": "RPC_UserP@SSW0RD",
  "mmrpc": "2.0",
  "method": "task::enable_bch::init",
  "params": {
    "ticker": "BCH",
    "activation_params": {
      "bchd_urls": [
        "https://bchd.dragonhound.info"
      ],
      "mode": {
        "rpc": "Electrum",
        "rpc_data": {
          "servers": [
            {
              "url": "bch.imaginary.cash:50002",
              "protocol": "SSL"
            },
            {
              "url": "cashnode.bch.ninja:50002",
              "protocol": "SSL"
            },
            {
              "url": "bch.soul-dev.com:50002",
              "protocol": "SSL"
            },
            {
              "url": "electrum3.cipig.net:20055",
              "protocol": "SSL"
            }
          ]
        }
      },
      "slp_tokens_requests": [
        {
          "ticker": "USDF"
        },
        {
          "ticker": "ASLP-SLP",
          "required_confirmations": 3
        }
      ],
      "tx_history": true,
      "required_confirmations": 5,
      "requires_notarization": false,
      "address_format": {
        "format": "cashaddress",
        "network": "bitcoincash"
      },
      "utxo_merge_params": {
        "merge_at": 50,
        "check_every": 10,
        "max_merge_at_once": 25
      }
    }
  }
}

API-v2task::enable_bch::status

status

After running the task::enable_bch::init method, we 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)

Arguments

Parameter	Type	Description
task_id	integer	The identifying number returned when initiating the initialisation process.
forget_if_finished	boolean	If `false`, will return final response for completed tasks. Optional, defaults to `true`.

Command

POST

task::enable_bch::status

{
  "userpass": "RPC_UserP@SSW0RD",
  "mmrpc": "2.0",
  "method": "task::enable_bch::status",
  "params": {
    "task_id": 0,
    "forget_if_finished": false
  }
}

Response (ready, successful, HD mode)

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.
.ticker	string	The ticker of the coin being activated
.current_block	integer	The block height of the coin being activated
.wallet_balance	object	Information about the addresses of the coin being activated
..wallet_type	string	In Trezor mode, this will return `HD`
..accounts	list	A list of addresses and related information for the coin being activated
...account_index	integer	`ACCOUNT_ID` child in the `m/44'/COIN'/ACCOUNT_ID'/CHAIN/ADDRESS_ID` BIP44 derivation path. Please don't confuse with kdf global Iguana/HD/HW account.
...derivation_path	string	Derivation path up to the `COIN` child. E.g. `"m/44'/141'/0'"`
...total_balance	object	Combined total spendable and unconfirmed balances of all account addresses
....spendable	string(numeric)	Combined total spendable balance of all account addreesses
....unspendable	string(numeric)	Combined total unspendable balance of all account addreesses
...addresses	list	A list of addresses in the account for the coin being activated
....address	string	One of the addresses in the account for the coin being activated
....derivation_path	string	The BIP44 derivation path of the address.
....chain	string	Returns `External` when `CHAIN=0` in the `m/44'/COIN'/ACCOUNT_ID'/CHAIN/ADDRESS_ID` derivation path. Returns `Internal` when `CHAIN=1` in the `m/44'/COIN'/ACCOUNT_ID'/CHAIN/ADDRESS_ID` derivation path. External is used for addresses that are meant to be visible outside of the wallet (e.g. for receiving payments). Internal is used for addresses which are not meant to be visible outside of the wallet and is used for return transaction change.
....balance	object	Contains the spendable and unspendable balance for this address
.....spendable	string(numeric)	Spendable balance for this address
.....unspendable	string(numeric)	Unspendable balance for this address (e.g. from unconfirmed incoming transactions)

Response (ready, successful, Iguana mode)

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.
.ticker	string	The ticker of the coin being activated
.current_block	integer	The block height of the coin being activated
.wallet_balance	object	Information about the addresses of the coin being activated
..wallet_type	string	In Trezor mode, this will return `HD`
..address	string	One of the addresses in the account for the coin being activated
..balance	object	Contains the spendable and unspendable balance for this address
...spendable	string(numeric)	Spendable balance for this address
...unspendable	string(numeric)	Unspendable balance for this address (e.g. from unconfirmed incoming transactions)

Response (in progress)

Parameter	Type	Description
status	string	Will return `InProgress` if task is not yet comepleted
details	string	An indication of the current step of the activation process

Possible In Progress Cases:

ActivatingCoin: The first step of activation. It does not require any action from the user.
RequestingWalletBalance: The first step of activation, while initial balances info is being requested. It does not require any action from the user.
Finishing: Activation process completed
WaitingForTrezorToConnect: Waiting for the user to plugin a Trezor device
FollowHwDeviceInstructions: Waiting for the user to follow the instructions on the device

Response (ready, error)

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 coin 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	Additonal context for the error type

Possible Error Cases:

TaskTimedOut - Timed out waiting for coin activation, connecting to the device trezor or for user to confirm pubkey)
CoinCreationError - Error during activation. E.g. incorrect or inactive electrum servers.
HwError - This is the most important error type. Unlike other error types, HwError requires the GUI / User to check the details in error_data field to know which action is required. View the HwError error type details for more info.

API-v2task::enable_bch::user_action

user_action

If the task::enable_bch::status returns UserActionRequired, we need to use the task::enable_bch::user_action method to enter our PIN

Arguments

Parameter	Type	Description
task_id	integer	The identifying number returned when initiating the initialisation process.
user_action	object	Object containing the params below
user_action.action_type	string	Will be `TrezorPin` for this method
user_action.pin	string (number)	When the Trezor device is displaying a grid of numbers for PIN entry, this param will contain your Trezor pin, as mapped through your keyboard numpad. See the image below for more information.

Response

Parameter	Type	Description
result	string	The outcome of the request.

📌 Examples

Command

POST

task::enable_bch::user_action

{
  "userpass": "RPC_UserP@SSW0RD",
  "mmrpc": "2.0",
  "method": "task::enable_bch::user_action",
  "params": {
    "task_id": 0,
    "user_action": {
      "action_type": "TrezorPin",
      "pin": "862743"
    }
  }
}

API-v2task::enable_bch::cancel

cancel

If you want to cancel the enabling process before it has completed, you can use this method.

Arguments

Structure	Type	Description
task_id	integer	The identifying number returned when initiating the enabling process.

Response

Structure	Type	Description
result	string	Indicates task cancellation was succesful.
error	string	An error message to explain what went wrong.
error_path	string	An indicator of the class or function which reurned the error.
error_trace	string	An indicator of where in the source code the error was thrown.
error_type	string	An enumerated value for the returned error.
error_data	string	The input task ID which resulted in the error.

POST

task::enable_bch::cancel

{
  "userpass": "RPC_UserP@SSW0RD",
  "method": "task::enable_bch::cancel",
  "mmrpc": "2.0",
  "params": {
    "task_id": 3
  }
}

On this page

task::enable_bch