账本存证
储值与筹码的账本每天封存为一个指纹,与前一天的指纹相连,并通过 OpenTimestamps 在比特币区块链上加盖时间戳。任何人都可以核对已公布的历史没有被改动;你也可以核对自己的每一笔记录都在其中。基于 Orbit。
公开哪些内容
- 每天:当天全部账本记录的指纹、前一天的指纹,以及记录条数。
- 每个指纹的时间戳证明,通常在一天内于比特币区块中确认。
绝不公开:姓名、邮箱、账户 ID、金额或余额。每条记录以私密化名计算指纹,外部无法将其与账户对应。
核对证明文件
选择在这里下载的证明文件(.json)。文件不会上传。
你的记录
每日指纹
存证 56 · 2026-11-20
存证 55 · 2026-11-19
存证 54 · 2026-11-18
存证 53 · 2026-11-17
存证 52 · 2026-11-16
存证 51 · 2026-11-15
存证 50 · 2026-11-14
存证 49 · 2026-11-13
存证 48 · 2026-11-12
存证 47 · 2026-11-11
存证 46 · 2026-11-10
存证 45 · 2026-11-09
存证 44 · 2026-11-08
存证 43 · 2026-11-07
存证 42 · 2026-11-06
存证 41 · 2026-11-05
存证 40 · 2026-11-04
存证 39 · 2026-11-03
存证 38 · 2026-11-02
存证 37 · 2026-11-01
存证 36 · 2026-10-31
存证 35 · 2026-10-30
存证 34 · 2026-10-29
存证 33 · 2026-10-28
存证 32 · 2026-10-27
存证 31 · 2026-10-26
存证 30 · 2026-10-25
存证 29 · 2026-10-24
存证 28 · 2026-10-23
存证 27 · 2026-10-22
存证 26 · 2026-10-21
存证 25 · 2026-10-20
存证 24 · 2026-10-19
存证 23 · 2026-10-18
存证 22 · 2026-10-17
存证 21 · 2026-10-16
存证 20 · 2026-10-15
存证 19 · 2026-10-14
存证 18 · 2026-10-13
存证 17 · 2026-10-12
存证 16 · 2026-10-11
存证 15 · 2026-10-10
存证 14 · 2026-10-09
存证 13 · 2026-10-08
存证 12 · 2026-10-07
存证 11 · 2026-10-06
存证 10 · 2026-10-05
存证 9 · 2026-10-04
存证 8 · 2026-10-03
存证 7 · 2026-10-02
存证 6 · 2026-10-01
存证 5 · 2026-09-30
存证 4 · 2026-09-29
存证 3 · 2026-09-28
一天中的一部分:当天其余部分在下一个存证中。
存证 2 · 2026-09-28
一天中的一部分:当天其余部分在下一个存证中。
存证 1 · 2026-09-27
如何核对
使用开源的 OpenTimestamps 客户端:
- 把某个存证的记录与时间戳证明下载到同一个文件夹。
- 安装客户端:
pip install opentimestamps-client
- 查看证明内容:
ots info credits-anchor-56.txt.ots
- 等待比特币区块期间,获取完整证明(会更新该文件):
ots upgrade credits-anchor-56.txt.ots
- 确认后,用你自己的比特币节点核对:
ots verify credits-anchor-56.txt.ots
- 没有节点时:客户端会列出区块号和要在任一区块浏览器中核对的值:
ots --no-bitcoin verify credits-anchor-56.txt.ots
- 每条记录的「prev」行是前一条记录的 SHA-256:
shasum -a 256 credits-anchor-55.txt # macOS sha256sum credits-anchor-55.txt # Linux
- 你某条记录的证明是一个 JSON 文件。可在本页核对,也可按下面的规范手动核对。
规范
规范以英文为准。
Lines. One line per posting of every entry created in the period (both currencies; test-account entries excluded):
yzc-leaf-v1|<entry id>|<account pseudonym>|<USD or CHIPS>|<amount>|<balance after>|<created at>|<idempotency key hash>
- Amounts are integers: micro-US-dollars for USD (1 USD = 1,000,000), whole Chips for CHIPS; negative for money leaving the account.
- The account pseudonym (32 hex) and the idempotency key hash (64 hex) are HMAC-SHA-256 values under a private key, so they cannot be linked to an account from outside.
- Lines are sorted by created at, then entry id, then pseudonym.
Tree. Line hash = SHA-256(0x00 ‖ UTF-8 line). Node = SHA-256(0x01 ‖ left ‖ right). Pairs are formed left to right on each level; an odd last node moves up unchanged. An empty period has the fingerprint SHA-256 of nothing (e3b0c442…b855). A proof path lists, from the line upwards, each sibling and the side it is on (L or R).
Record. The text that is timestamped, UTF-8 with a newline after each line:
YunZheng Credits ledger anchor v1 seq: <n> window: <start>/<end> entries: <entries> leaves: <lines> merkle_root: <fingerprint of the entries> prev: <anchor fingerprint of seq n-1, or 64 zeros>
Anchor fingerprint = SHA-256 of the record. It is submitted to several public OpenTimestamps calendars; the .ots file is the combined proof. Periods are consecutive, each within one UTC day.