Colo may refer to: Places Colo (volcano), in Indonesia Colo, Iowa, United States Colo, New South Wales, Australia Colo River, in Australia Colo., an abbreviation for the U.S. state of Colorado A form
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 0xebad3ae07377aa34d058adaaef705b46c40da3cff7a41113c8596f930f1eb701. Chain 2 (Bitcoin): anchored in block 954066 (2026-06-17T08:11:48Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/6d1eda0f-0e90-4c65-9331-d25f8ef31a0c.json and https://artists.proofprofile.net/proofs/artist/6d1eda0f-0e90-4c65-9331-d25f8ef31a0c.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 0xe18ad509ab387e9e3b663a97cbd60c8bf13f77f580db0499aec0f8b4809e266c. Chain 2 (Bitcoin): anchored in block 958392 (2026-07-17T09:46:31Z), 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/QZK6N2444489.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb1dccc244edde3987c697bd4c8447b91ed6702506870733c20cf0402c51a69a2. Chain 2 (Bitcoin): anchored in block 958594 (2026-07-18T18:05: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/QZHN32504724.