Kolo may refer to: Places Poland Koło Koło, Łódź Voivodeship Koło, Lublin Voivodeship Koło, Lubusz Voivodeship Koło, Warsaw Other places Kamalanka, which was also known as Kolo, an ancient kingdom i
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 0x0203d0379e92f3208d3ca9a594fe4f08f5a103f726ce5c739975c8b57980dadc. Chain 2 (Bitcoin): anchored in block 953407 (2026-06-12T19:24:56Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/1d14a2e5-4d8e-428e-ae06-9283eafc693f.json and https://artists.proofprofile.net/proofs/artist/1d14a2e5-4d8e-428e-ae06-9283eafc693f.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 0x99433e6fffe003def0db8dbeb1a1f3fb3a8b9020849495ae94df9fd881726bde. Chain 2 (Bitcoin): anchored in block 956856 (2026-07-06T01:25:57Z), 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/NL1AP2061084.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb37b0722bf478c297f69d3ec84a809e6024aaf663657b01a3c9e4e57c84f4df0. Chain 2 (Bitcoin): anchored in block 958639 (2026-07-19T01:18:30Z), 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/FRIDO2312221.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb0141777237bf6dfd7ff7f2f9fb4bbd7adad2e52437fbe77f2f304e6a946708c. Chain 2 (Bitcoin): anchored in block 953515 (2026-06-13T12:53:06Z), 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/FRPZ92417280.