Loko may refer to: Port Loko, Sierra Leone, Africa Loko people, a people of Sierra Leone Loko language, a language of Sierra Leone Loco (loa) or Loko, a figure in Haitian Vodou belief Loko, a go
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 0x4007054631287293a03eaeac4ecb8095e235141df25225e84a073345f6200a50. Chain 2 (Bitcoin): anchored in block 953791 (2026-06-15T13:40:30Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/de3ad398-a5b6-44ea-b4a2-168153625b0f.json and https://artists.proofprofile.net/proofs/artist/de3ad398-a5b6-44ea-b4a2-168153625b0f.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 0x96db5313b71c5b0f264e4cb5e466c6d88476566785bac7c3d5bcd10d0c38ba37. Chain 2 (Bitcoin): anchored in block 956725 (2026-07-05T01:12: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/QZFZ72598156.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa4e59b724d0acec9ab8c004e31d4573ee057b3b3077a4339f052d0c8af91ef6a. 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/QZK6J2526084.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x434a6b13aaea7edff666f89821b4b57c537393a5ee49f14fc7ab3883b176c070. Chain 2 (Bitcoin): anchored in block 958876 (2026-07-20T12:15:48Z), 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/QZZ7R2545904.