Token Locks

All endpoints return the following response headers:

X-Id — The node’s public key identifier
X-Session-Token — The current cluster session token
Request-Signature — Cryptographic signature of the response for verification

GET /token-locks

Returns all active token locks for a given address, as recorded in the latest global snapshot.

curl "https://<node-host>:9000/token-locks?address=DAG3hZTBgtb2iH9ZdLNvaKqPT4ZncCuW6uYxZack"

address

string

required

The DAG wallet address to query for active token locks

Response 200 OK

Returns an array of TokenLock objects.

[]

array

Array of active token lock objects

Show TokenLock

source

string

Source wallet address that created this token lock

amount

integer

Locked amount in datums

fee

integer

Fee paid for the lock transaction, in datums

parent

object

Reference to the parent token lock transaction

Show TokenLockReference

ordinal

integer

Ordinal number of the parent transaction

hash

string

Hash of the parent transaction

currencyId

string

Currency identifier for the token lock. null for DAG locks.

unlockEpoch

integer

Epoch at which the tokens unlock. null for indefinite locks (used for staking).

replaceTokenLockRef

string

Hash of an existing token lock that this one replaces (for increasing an existing lock). null for new locks.

Example response:

[
  {
    "source": "DAG3hZTBgtb2iH9ZdLNvaKqPT4ZncCuW6uYxZack",
    "amount": 25000000000,
    "fee": 0,
    "parent": {
      "ordinal": 0,
      "hash": ""
    },
    "currencyId": null,
    "unlockEpoch": null,
    "replaceTokenLockRef": null
  }
]

Response 503 Service Unavailable

Node is not in Ready state.

Global L0 Node

DAG L1 Node

Currency Metagraph

GET /token-locks

Build docs developers (and LLMs) love

Global L0 Node

DAG L1 Node

Currency Metagraph

​GET /token-locks

Build docs developers (and LLMs) love

GET /token-locks