Yizi or Yi Zi may refer to: Places Yizi Subdistrict, Panzhou, Guizhou, China Yizi Hutong, Shichahai, Beijing, China; a historic hutong villa Yizi Lane, Haishu, Ningbo, Zhejiang, China; near Daqing
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 0xd4981c00ec534d7c5ca64eb5c75530fc0be6ad14cea000216ecc88c4067a861f. Chain 2 (Bitcoin): anchored in block 954014 (2026-06-16T22:46:20Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/293e31b9-49c7-4452-b473-349d719c035f.json and https://artists.proofprofile.net/proofs/artist/293e31b9-49c7-4452-b473-349d719c035f.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
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 0xa67ddf45844b8d3cc2887fcad43d545b3b8e9cb9187bb8a053b550d35ee47f3c. Chain 2 (Bitcoin): anchored in block 957120 (2026-07-08T03:22:41Z), 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/QZNJV2440088.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x64585366481cbef98c44fc096ea9cad44809ea5f50e38d13aed870b86dd02cf4. Chain 2 (Bitcoin): anchored in block 957120 (2026-07-08T03:22:41Z), 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/QZNJV2440090.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x6a867df1d2555d9d13ba0b7a39af21df0c9fa721bbd4b8bc34d507d1b5d9a6b2. Chain 2 (Bitcoin): anchored in block 957020 (2026-07-07T09:18:01Z), 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/QM7282341399.