HALO, halo, halos or haloes may refer to: Most commonly Halo (optical phenomenon), with ice crystals Halo (religious iconography), a ring of light around the image of a head Halo (franchise), a sc
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 0x9281ca5397d9b0f0c94f42bf7a98a7cd7739cc10eef546383b075c0c5ed83c69. 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/2b61a076-3f0d-4b11-a301-aa4bafa648b8.json and https://artists.proofprofile.net/proofs/artist/2b61a076-3f0d-4b11-a301-aa4bafa648b8.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 0xdfbbfd175b00dab387cce041a3ff9a0db3b0fa005504a7bbc57b47974b018055. Chain 2 (Bitcoin): anchored in block 958316 (2026-07-16T19:42:29Z), 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/GB7GV1851103.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x504a86bd6664f75150186ff384f5807bf4f152fabda7697ab9b89287e33eb263. Chain 2 (Bitcoin): anchored in block 958211 (2026-07-15T23:24:33Z), 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/GB7GV2262221.