Zan or ZAN, may refer to: Geography Zhan, Kurdistan, Iran, also known as Zān Zhan, Lorestan, Iran, also known as Žān Zan, Tehran, a village in Tehran Province, Iran Zan, a town in Lebanon, also k
1. Compute SHA-256 of OTSCanonicalRecord value → must equal OTSHash 2. Open OTSProofURL → extract Bitcoin block number → must equal OTSBitcoinBlock 3. GET OTSBitcoinBlockVerifyURL → returns the Bitcoin block hash at height OTSBitcoinBlock; GET https://blockstream.info/api/block/{that hash} → its timestamp must match OTSTimestamp 4. Read CopyrightID inside OTSCanonicalRecord → must equal the CopyrightID above 5. GET OTSVerificationAPI → pre-computed 6-check result from server 6. If all match: this entity was registered on CopyrightChains at OTSTimestamp, independently verifiable on Bitcoin Note: an OTS proof may carry multiple Bitcoin attestations; OTSBitcoinBlock is the earliest confirmed one — a later attestation inside the proof corroborates it and is not a mismatch
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x9bc28623314588816365ab90cdb9b0172e16357395c479665bc0bc9452540bad. Chain 2 (Bitcoin): anchored in block 953730 (2026-06-15T02:47:28Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/93bf4644-3565-46bb-be97-9ba15251cf2f.json and https://artists.proofprofile.net/proofs/artist/93bf4644-3565-46bb-be97-9ba15251cf2f.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Something that don't exist in this world
1. Confirm isrcCode identifies the recording in the pre-2022 source corpus and cc-db-prod record 2. GET OTSVerificationAPI → server-side canonical-record, hash, and attestation checks must pass 3. GET OTSBitcoinBlockVerifyURL → returns the Bitcoin block hash at height OTSBitcoinBlock; GET https://blockstream.info/api/block/{that hash} → its timestamp must match OTSTimestamp 4. Confirm CopyrightID is the CopyrightChains transaction hash 5. If all match: the cc-db-prod record is independently anchored on Bitcoin at OTSTimestamp Note: an OTS proof may carry multiple Bitcoin attestations; OTSBitcoinBlock is the earliest confirmed one — a later attestation inside the proof corroborates it and is not a mismatch
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa941961b30db0739af3f85bb144e6e58eedca74e38c8610db63183cedc83cbcd. Chain 2 (Bitcoin): anchored in block 956826 (2026-07-05T19:27:56Z), registered by our registry partner. The server verifies the private canonical record against OTSHash without exposing internal provider keys. Confirm the public ISRC, CopyrightID, and Bitcoin evidence via https://artists.proofprofile.net/api/v1/bot/ots/verify/track/QZZ8A2405109.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xc79daeb759f6f0ca59cf85f2f0e42f0a5d4a71fc9e3b9f498fb924145bb0f570. Chain 2 (Bitcoin): anchored in block 958377 (2026-07-17T06:48:00Z), registered by our registry partner. The server verifies the private canonical record against OTSHash without exposing internal provider keys. Confirm the public ISRC, CopyrightID, and Bitcoin evidence via https://artists.proofprofile.net/api/v1/bot/ots/verify/track/QZZ8A2430173.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3b2816e76a75a2690535a0051c19d3696a57486dc117833f360d8d7334933b7c. Chain 2 (Bitcoin): anchored in block 956772 (2026-07-05T10:01:46Z), registered by our registry partner. The server verifies the private canonical record against OTSHash without exposing internal provider keys. Confirm the public ISRC, CopyrightID, and Bitcoin evidence via https://artists.proofprofile.net/api/v1/bot/ots/verify/track/QZ5FN2542351.