Zcash commands

Call a command as POST /v1/zcash/{command}. Coverage: transparent transactions from 2016-10-28 to max_block, with wallet clusters. Zcash takes the Bitcoin commands with the same options, limits and answer shapes.

Node forms: a transparent address (t1... or t3..., 35 characters), a numeric id from resolve, cluster:<address>, cluster:#<id>, or one of the shielded pools z:sprout, z:sapling and z:orchard.

Amounts: in zatoshi (1 ZEC = 100,000,000 zatoshi) where Bitcoin uses satoshi, so min-sat and min-taint-sat take zatoshi. Trace fields keep their Bitcoin names (seed_btc, taint_btc, accounting_btc) and hold ZEC.

Shielded pools

The graph sees only the transparent side. Sending to a shielded address is an output to z:sprout, z:sapling or z:orchard; withdrawing from one is an input from that pool. Nothing links a deposit to a later withdrawal. Amounts at a pool boundary are estimated and approximate.

addr, utxo, cluster and trace refuse a pool with invalid_address. A trace stops where taint enters a pool, and a pool cannot be the source.
resolve, neighbors and topk accept a pool, but a pool holds millions of outputs and is usually over the scan cap. For one address’s shieldings and unshieldings, query the address: neighbors with {"counterparty": "z:sapling"} (or another pool).
In neighbors rows, a pool appears as the counterparty z:sprout, z:sapling or z:orchard.

Commands

Command	Input	`targets`	Weight
`info`	none	–	light
`resolve`	1–1,000 nodes	–	light
`addr`	1 address	up to 200	light
`utxo`	1 address	–	light
`tx`	`<block> <tx_index>`	up to 200	light
`cluster`	1 address or cluster	–	light
`neighbors`	1 node	up to 200	heavy
`topk`	1 node	up to 200	heavy
`trace`	1 address	–	heavy

The options are those of the Bitcoin commands; counterparty and pin-addr take Zcash addresses.

Notes

tx with {"positional": ["<block>", "<tx_index>"]} shows every input and output. The input of a withdrawal from a pool points at a pool output whose block is a placeholder, not the time anything happened.
Clusters change as new transactions arrive. Compare _meta.dataset.generation before comparing cluster sizes across days.