Niha may refer to: Places Lebanon Niha, Chouf Fortress of Niha Niha, Zahlé Hosn Niha, an archaeological site Niha, Batroun Syria Niha, Idlib Niha, Tartus Other uses Nepal Ice Hockey Associat
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 0xdb84b9bd2e69c67d270645414f3517511c944f9218ff11ebb517cf7024b91dfe. Chain 2 (Bitcoin): anchored in block 953713 (2026-06-15T00:33:41Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/83ea60d6-1ffb-4a54-b041-672daf9655fc.json and https://artists.proofprofile.net/proofs/artist/83ea60d6-1ffb-4a54-b041-672daf9655fc.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 0x1324a61faaf36320e910dc3b0fa5342769f1679b933a765be18a4960a380dd63. Chain 2 (Bitcoin): anchored in block 956545 (2026-07-03T19:59:51Z), 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/TCJPE1670766.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x59814fcc88bf6c8d20ac4c7adcea3f1e9e3b6dcde891401ecd1142a6c9faa051. Chain 2 (Bitcoin): anchored in block 958529 (2026-07-18T09:21: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/TCJPE1670768.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x59814fcc88bf6c8d20ac4c7adcea3f1e9e3b6dcde891401ecd1142a6c9faa051. Chain 2 (Bitcoin): anchored in block 958582 (2026-07-18T16:47:25Z), 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/TCJPE1670768.