Naz or NAZ may refer to: Naz (name) NAZ (studio), Japanese animation studio Naz, Iran, a village in Hormozgan Province, Iran Naz, Switzerland, in the canton of Vaud Naaz islands, a set of tidal
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 0xa923601aa3b123638b1c68fe94649e39ec545244849193378e4f49e3d681d4da. Chain 2 (Bitcoin): anchored in block 953746 (2026-06-15T05:25:34Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/a45013b1-a2fc-4b62-bd91-9673133cd104.json and https://artists.proofprofile.net/proofs/artist/a45013b1-a2fc-4b62-bd91-9673133cd104.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 0x50daff167cc11593b1cf8a7c718e709fda742f4b42f5b432dfc7ea3696421c2b. Chain 2 (Bitcoin): anchored in block 958538 (2026-07-18T10:30:13Z), 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/QZMEQ2156899.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xf4003d2f9f7fcd376dd4ed18faa5c23e690b91b070d69e52665f928100209b82. Chain 2 (Bitcoin): anchored in block 958680 (2026-07-19T06:04:14Z), 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/FINIG2400028.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x93a3e846bca4c7489d987e7f061563cf8337d8b001aa2840d68c80cc9c2e8a71. Chain 2 (Bitcoin): anchored in block 956725 (2026-07-05T01:12: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/FINIG2400035.