UTXO assets enpoint

[mkpuig]

Hello, I'm wondering if there's an equivalent to rpc {"method":"gettxout",params:[ txid, vout, true]} on any service on teranode, because the /api/v1/utxo/:hash/json?vout=N even launching in parallel is a lot slower than bulk rpc commands

(Or if is it planned sometime to allow a POST bulk request, just like POST /api/v1/txs )

Thank you in advance!

[icellan]

Hi @mkpuig that's a great idea. I've implemented this. It will be added to the next version of Teranode.

#950

[mkpuig]

Thank you!
Could it be possible also for /api/v1/utxos/:hash/json?

Thank you!

[icellan]

The PR includes /api/v1/utxos where you would post the outpoints in binar and get a response in binary or JSON back

POST /api/v1/utxos — Binary. Concatenated fixed-length 48-byte records in input order, each [8 bytes status LE][4 bytes lockTime LE][4 bytes spendingVin LE][32 bytes spendingTxID]. Unspent UTXOs have the trailing 36 bytes zero-filled; not-found records report status utxo.Status_NOT_FOUND. Clients can index by i*48.

• POST /api/v1/utxos/hex — Lowercase hex-encoding of the binary response. Same record layout once decoded.
• POST /api/v1/utxos/json — JSON array of utxo.SpendResponse objects in input order, e.g. [{"status":1,"spendingData":{"txId":"...","vin":0},"lockTime":1234567}, ...]. Use this when client tooling prefers JSON; for highest throughput, prefer the binary route.
  • Limits: body size capped by the asset_httpBodyLimit setting (default 4MB ≈ 116k records per request).
  • Error responses: 400 (body length not a multiple of 36), 413 (body exceeds the cap), 500 (transport or store failure).