Hidra may refer to: Places Hidra, Tunisia, a municipality in the Kasserine Governorate, Tunisia Hidra, Vest-Agder, a former municipality in Vest-Agder county, Norway Hidra (island), an island in Flek
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 0x4d79dffb262a35ce85b17230c32842d65cba791b8ee894a132d6115a4904fae7. Chain 2 (Bitcoin): anchored in block 953625 (2026-06-14T11:37:06Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/2302d06e-81e1-4466-b3ea-b9b77268dfb8.json and https://artists.proofprofile.net/proofs/artist/2302d06e-81e1-4466-b3ea-b9b77268dfb8.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 0x39f8844766bbcf330306f4f108db58b8a4e99d3123dc645413de3b547f4ebca3. Chain 2 (Bitcoin): anchored in block 958245 (2026-07-16T05:50:22Z), 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/USQY51221546.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x4c3d28a118ded107edcb7cef3a10129d199eefff6d695a4b9e87839b4f77a0b6. Chain 2 (Bitcoin): anchored in block 956822 (2026-07-05T18:48:28Z), 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/USQY51221547.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xbfd164faaf9fa15f98374d05f73d9f960166c760defa48952a331b2d48b73c0c. Chain 2 (Bitcoin): anchored in block 956822 (2026-07-05T18:48:28Z), 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/USCGJ2597383.