Koza may refer to: Places Koza, Opole Voivodeship, a village in south-west Poland Koza, Wakayama, a Japanese town, merged in 2005 into Kushimoto Kōza District, Kanagawa, a Japanese district in Kan
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 0x73f7ad8aa5c48a7b7f759a248ccd53bd271ab7f84ef402b7de2bd42a3e3135e2. Chain 2 (Bitcoin): anchored in block 953903 (2026-06-16T07:05:05Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/144ded66-7adf-4c68-b797-4009471e9b8f.json and https://artists.proofprofile.net/proofs/artist/144ded66-7adf-4c68-b797-4009471e9b8f.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 0x0f64cfe49b42c33cbb111d7e4c90e07979eb00f9021b1f04400a3c251fd9daf8. Chain 2 (Bitcoin): anchored in block 958942 (2026-07-21T00:24:07Z), 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/FR9W12508483.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xe6a997d024e67c4614157115c9bb90d259cf90fa3f487ea4ddb182b79eea2f62. Chain 2 (Bitcoin): anchored in block 956772 (2026-07-05T10:01:46Z), 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/FR9W12531681.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x8cba90ffefdb5e813fd40bfea233d2313f40b11a47064e3ca679dc88442ec860. Chain 2 (Bitcoin): anchored in block 958924 (2026-07-20T18:54:07Z), 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/FR9W12542480.