Z-DAG for UTXO asset payments
Z-DAG (Zero-Confirmation Directed Acyclic Graph) was designed for Syscoin Platform Token payments. A recipient can use a Core node’s view of the transaction and its dependencies to get an early indication that a payment is progressing. The recipient chooses when to act on that evidence. Proof-of-work inclusion and ChainLocks supply later assurances through the normal block path. Z-DAG whitepaper · Syscoin Platform Tokens
Why check the ancestors of a payment?
Take the supplier who received 7 tokens in the workshop example. The supplier pays a courier with that output before the workshop payment confirms. If the workshop’s original input also funds a competing transaction, the courier’s payment depends on which spend gets into the chain. The courier can ask Core about its own incoming payment and receive a warning about a conflict one transaction earlier.
The courier queries the supplier-to-courier transaction ID. Core checks that transaction and its unconfirmed ancestors in the node’s local mempool view. A known double spend can produce status 4. After the recipient’s chosen wait, only 0 qualifies for early acceptance under Z-DAG. For every other result, check the transaction on the active chain and apply the recipient’s confirmation policy. A missing mempool entry can mean the payment already confirmed. Current status check · RPC status reference
The eligible Core transaction type is SPT allocation send, version 142. Ordinary native SYS payments, NEVM transfers, asset mints, and bridge burns use their own confirmation or settlement path. Core #609 retains specific conflict warnings and adds status 5 when the node has exhausted its budget for keeping conflict evidence. The Z-DAG developer guide explains the statuses and the recommended fallback. Transaction eligibility · Core and finality
Whiteblock’s Core 4 tests measured how quickly unconfirmed asset payments propagated as network latency changed. A merchant still chooses how long to wait before honoring an eligible payment and when to require block confirmation. Measured Z-DAG results · Whiteblock performance report