Substantive changes to the manifest spec, the verification path, and the platform around it. Minor fixes live in the git history.
Every new seal is stamped to four public OpenTimestamps calendars at sealing time. A daily sweep upgrades pending proofs once Bitcoin confirms the commitment, and the BitSeal SDK ships a --ots flag so anyone can re-check the anchor against mempool.space without trusting Orygn.
SHA-256 of each seal's signature is submitted to four public calendars at seal time.
Pending proofs upgrade automatically once any calendar's commitment lands in a Bitcoin block, typically within 1 to 6 hours.
/verify renders block height, block time, and a mempool.space deep-link once the seal's anchor is upgraded.
verify.py --ots parses the upgraded proof locally and compares the committed merkle root against the real block header via mempool.space.
First public release of the BitSeal platform. Client-side hashing, three-axis verification, and signed manifests, wired through a Neon Postgres ledger.
Browser-only BLAKE3 over 64 KiB chunks, files never leave the device.
Signed seal record rendered to a downloadable PDF on request.
GET /api/verify returns the three-axis verdict over any root hash.
Seals persist to Neon Postgres; verify reads from the same store.
Closed alpha validating the Merkle construction and signing payload against the BitSeal SDK. Format frozen at merkle-blake3-64k-v1.
64 KiB leaves, BLAKE3 internal nodes, odd-layer-duplicate rule.
40 bytes, root || LE_f64(timestamp), over Ed25519.