Verify

Every item’s identity is a hash of a string we publish. Recompute it, then look for it inside the issuance transaction on a node ZecBit does not operate. Nothing here trusts us.

TRY ONE

zmd1|zecbit-genesis|1 zmd1|zecbit-genesis|2 zmd1|zecbit-genesis|3 zmd1|zecbit-genesis|4 zmd1|zecbit-genesis|5

Do it yourself

Four lines of standard-library Python, no dependencies. This is the whole of what makes an item’s identity — there is nothing else to trust.

from hashlib import blake2b

desc = b"zmd1|zecbit-genesis|1"
print(blake2b(desc, digest_size=32, person=b"ZSA-AssetDescCRH").hexdigest())

Then look for that hash in the transaction, on whichever node you like:

curl -s -X POST https://dev.zebra.zsa-test.net \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getrawtransaction",
       "params":["611ddfd4459e813b86b935fc05217f929e29c37cdc96ba8f23fc647e30c26317",1]}'

What this proves: the item exists and was issued by the key that signed that transaction. What it deliberately cannot show: who holds it. Ownership is a shielded note, invisible to this page and to us.

Checking ownership without us

Everything above proves an item exists. This proves who it was assigned to — and it is the part that has to keep working if ZecBit does not. Assignments are summarised into one hash, that hash is written into a Zcash transaction, and the data behind it is published. A holder keeps a certificate; anyone can then rebuild the hash from the published data and check the certificate against it, with nothing of ours running.

No snapshot has been published yet.