Transactions

DAG L1 transactions are the primary mechanism for transferring $DAG tokens between addresses. Transactions are submitted to an L1 node, validated, assembled into blocks, and eventually finalized in a global snapshot.

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

Building a valid transaction: Each transaction must reference its parent — the previous transaction from the same source address. Use GET /transactions/last-reference/{address} to retrieve the correct parent.hash and parent.ordinal before constructing a new transaction. The new transaction’s ordinal must be exactly parent.ordinal + 1.

POST /transactions

Submits a signed $DAG transaction for processing. If accepted, the transaction enters the node’s mempool and will be included in the next block.

curl -X POST https://<node-host>:9010/transactions \
  -H "Content-Type: application/json" \
  -d '{
    "value": {
      "source": "DAG3hZTBgtb2iH9ZdLNvaKqPT4ZncCuW6uYxZack",
      "destination": "DAG2rMPHX4w1cMMJowmewRMjD1in53yRURt6Eijh",
      "amount": 100000000,
      "fee": 0,
      "parent": {
        "hash": "",
        "ordinal": 0
      },
      "salt": 6018762703199813000
    },
    "proofs": [
      { "id": "<public-key-hex>", "signature": "<ecdsa-der-hex>" }
    ]
  }'

Request body — SignedTransaction

value

object

required

The transaction payload

Show Transaction

source

string

required

Source wallet address (must begin with DAG)

destination

string

required

Destination wallet address (must be different from source)

amount

integer

required

Amount to transfer in datums (1 DAG = 100,000,000 datums)

fee

integer

required

Transaction fee in datums (can be 0 subject to rate limits)

parent

object

required

Reference to the previous accepted transaction from the source address

Show TransactionReference

hash

string

required

Hash of the parent transaction. Use empty string "" for the first transaction.

ordinal

integer

required

Ordinal of the parent transaction. Use 0 for the first transaction.

salt

integer

required

Random 64-bit integer for uniqueness (prevents hash collisions between otherwise identical transactions)

proofs

array

required

Array of cryptographic signature proofs. Must be signed by the source address owner.

Show SignatureProof

string

required

Public key hex of the signing key

signature

string

required

ECDSA signature in DER format (hex-encoded)

Response 200 OK

hash

string

Hash of the accepted transaction. Use this to look up the transaction status via GET /transactions/{hash}.

Example response:

{
  "hash": "a1b2c3d4e5f6789012345678901234567890123456789012345678901234567890"
}

Response 400 Bad Request The transaction was rejected. The error response includes one of the following rejection reasons:

errors

array

Show Rejection reasons

TransactionLimited

string

The fee-less transaction rate limit for this address has been exceeded. The limit depends on the address balance and time elapsed since the last accepted transaction.

ParentOrdinalLowerThenLastTxOrdinal

string

The transaction’s parent ordinal is lower than the last accepted transaction’s ordinal. The new ordinal must be exactly lastOrdinal + 1.

HasNoMatchingParent

string

The parent hash does not match any known accepted transaction for this address.

InsufficientBalance

string

The transaction amount exceeds the source address balance.

AddressLocked

string

The source address is locked by the network and cannot send transactions.

Conflict

string

A transaction with this hash has already been accepted by the network.

SameSourceAndDestinationAddress

string

The source and destination addresses must be different.

NotSignedBySourceAddressOwner

string

The transaction signature does not correspond to the source address’s key.

GET /transactions/

Returns the current view of a $DAG transaction in the L1 mempool for the given hash. Only transactions currently in the mempool are returned — once a transaction is included in a block and a global snapshot, this endpoint returns 400.

curl https://<node-host>:9010/transactions/a1b2c3d4e5f6789012345678901234567890

hash

string

required

The transaction hash (hex-encoded SHA-256)

Response 200 OK

transaction

object

The full transaction data (see Transaction schema in POST /transactions)

hash

string

The transaction hash

status

string

Current status of the transaction in the mempool. Currently: Waiting

Example response:

{
  "transaction": {
    "source": "DAG3hZTBgtb2iH9ZdLNvaKqPT4ZncCuW6uYxZack",
    "destination": "DAG2rMPHX4w1cMMJowmewRMjD1in53yRURt6Eijh",
    "amount": 100000000,
    "fee": 0,
    "parent": { "hash": "", "ordinal": 0 },
    "salt": 6018762703199813000
  },
  "hash": "a1b2c3d4e5f6...",
  "status": "Waiting"
}

Response 400 Bad Request No transaction with the given hash is found in the mempool. The transaction may have already been processed into a block, or the hash may be invalid.

GET /transactions/last-reference/

Returns the last accepted $DAG transaction reference for a given address. Always call this endpoint before constructing a new transaction to get the correct parent values.

curl https://<node-host>:9010/transactions/last-reference/DAG3hZTBgtb2iH9ZdLNvaKqPT4ZncCuW6uYxZack

address

string

required

DAG wallet address

Response 200 OK

ordinal

integer

Ordinal of the last accepted transaction. Use ordinal + 1 as your new transaction’s parent ordinal.

hash

string

Hash of the last accepted transaction. Use this as your new transaction’s parent.hash. Returns empty string "" for addresses with no prior transactions.

Example response:

{
  "ordinal": 15,
  "hash": "a1b2c3d4e5f6789012345678901234567890"
}

Global L0 Node

DAG L1 Node

Currency Metagraph

POST /transactions

GET /transactions/

GET /transactions/last-reference/

Build docs developers (and LLMs) love

Global L0 Node

DAG L1 Node

Currency Metagraph

​POST /transactions

​GET /transactions/

​GET /transactions/last-reference/

Build docs developers (and LLMs) love

POST /transactions

GET /transactions/

GET /transactions/last-reference/