token

Token info — list all tokens with declaration/update history, or inspect a single token ticker.

JSON-RPC

Method name: token. Supports API version 1 (params string) and version 2 (subcommand + arguments).

Version 1 — semicolon params

{
  "jsonrpc": "2.0",
  "method": "token",
  "params": ["token;list;-net;Backbone"],
  "id": 1,
  "version": 1
}

Arguments are separated by ; only. Example: token;info;-net;Backbone;-name;CELL.

Version 2 — subcommand + arguments

{
  "method": "token",
  "subcommand": "list",
  "arguments": {"net": "Backbone"},
  "id": 1,
  "version": 2
}

{
  "method": "token",
  "subcommand": "info",
  "arguments": {"net": "Backbone", "name": "CELL", "history_limit": "10"},
  "id": 2,
  "version": 2
}

{"method":"ledger","subcommand":"list;coins","arguments":{"net":"Backbone","limit":"20"},"id":3,"version":2}

Global options

Subcommands

Example requests

Version 1

{"jsonrpc":"2.0","method":"token","params":["token;list;-net;Backbone"],"id":1,"version":1}

{"jsonrpc":"2.0","method":"token","params":["token;info;-net;Backbone;-name;CELL;-history_limit;10"],"id":2,"version":1}

Version 2

{"method":"token","subcommand":"list","arguments":{"net":"Backbone"},"id":1,"version":2}

{"method":"token","subcommand":"info","arguments":{"net":"Backbone","name":"CELL","history_limit":"10"},"id":2,"version":2}

Discover tickers on the public node via ledger list coins instead:

{"jsonrpc":"2.0","method":"ledger","params":["ledger;list;coins;-net;Backbone;-limit;20"],"id":3,"version":1}

{"method":"ledger","subcommand":["list","coins"],"arguments":{"net":"Backbone","limit":"20"},"id":4,"version":2}

Response envelope

{
  "type": 2,
  "result": [ ... ],
  "id": 1,
  "version": 1
}

Errors: result[0].errors[] with codes such as -name missing or token not found.

Version 1 vs version 2 response field names

Token history is built in dap_chain_node_cli_cmd_tx.c; per-token live state reuses dap_ledger_token_info_by_name (same fields as ledger list coins).

Inside current state / current_state, field names follow the same v1/v2 mapping as ledger list coins.

Response structure (from implementation)

Both list and info call dap_db_net_history_token_list (dap_chain_node_cli_cmd_tx.c). result[0] is an object:

• TOKENS (v1) or tokens (v2) — array of per-chain objects; each chain object maps ticker → token entry.
• tokens (uint64) — total token count across chains (list only; same key name in both versions).

Each token entry contains:

• current state (v1) / current_state (v2) — live ledger token info from dap_ledger_token_info_by_name (same fields as ledger list coins).
• declarations — array of declaration datums with status (ACCEPTED/DECLINED), Ledger return code (v1) / ledger_ret_code (v2), and nested Datum dump.
• updates — array of token-update datums (same shape).

list — expected shape (local node)

{
  "type": 2,
  "result": [
    {
      "TOKENS": [
        {
          "CELL": {
            "current state": {
              "-->Token name": "CELL",
              "type": "CF20",
              "Supply current": "0",
              "Supply total": "0",
              "Decimals": "18",
              "Auth signs valid": 4,
              "Auth signs total": 6,
              "flags": ["ALL_SENDER_ALLOWED"],
              "utxo_blocklist_count": 0,
              "Total emissions": 26898
            },
            "declarations": [
              {
                "status": "ACCEPTED",
                "Ledger return code": 0,
                "Datum": { "hash": "0x...", "type_id": "DATUM_TOKEN", "...": "..." }
              }
            ],
            "updates": []
          },
          "BUSD": { "...": "..." }
        }
      ],
      "tokens": 42
    }
  ],
  "id": 1,
  "version": 1
}

With version: 2, TOKENS becomes tokens (array), current state becomes current_state, and nested token fields use snake_case as in the mapping table above. TOKENS has one element per chain that contains token datums (e.g. zerochain on Backbone). Tickers are keys inside each chain object.

info — expected shape (local node)

Same object as list, but the token array contains only the requested ticker (or an error if not found).

{
  "result": [
    {
      "TOKENS": [
        {
          "CELL": {
            "current state": { "...": "..." },
            "declarations": [ "..." ],
            "updates": [ "..." ]
          }
        }
      ]
    }
  ]
}

current state / UTXO blocklist fields

When UTXO blocking is enabled, current state / current_state may include:

• utxo_blocklist_count
• utxo_blocklist array with tx_hash, out_idx, blocked_time, becomes_effective, becomes_unblocked (0 = permanent)
• history_recent / history_total_count per blocked UTXO (controlled by -history_limit)

Local CLI -h vs JSON-RPC response

JSON-RPC always returns the JSON object above; -h does not change the HTTP response (same as block and ledger). Local CLI uses s_print_for_token_list to print an ASCII table for token list ... -h.

With -full in local CLI, declaration hash column shows the full hash; otherwise last 10 characters.

Back to index