thumb|upright=1.20|Polish Lancer (left) and Austrian Cuirassier (right) in a mêlée A lancer was a type of cavalryman who fought with a lance. Lances were used for mounted warfare in Assyria as early a
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 0x959a426f53acfa6a5e915ec75d057dfffbae8f7834c0a84ba2f34e4bf795c774. 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/5f445f49-ae8b-4d3b-85e4-ce7f1298f02e.json and https://artists.proofprofile.net/proofs/artist/5f445f49-ae8b-4d3b-85e4-ce7f1298f02e.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 0x51b1936dd144f1b51e27abdf768383e1f4c734c373c2f00a47f042fb37c14d63. Chain 2 (Bitcoin): anchored in block 958951 (2026-07-21T05:00:34Z), 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/NLX9Z1800213.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x0f55fe58d493185f7bbcf57bca05f268d72a6d2a34be4ebc8660afb69327089e. Chain 2 (Bitcoin): anchored in block 958185 (2026-07-15T18:19:04Z), 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/NL8PU2400396.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3bcea37ceb5926d5a9e1f98715ceb6c5be480b3e60ecda9e52417b54dfbdd2ee. Chain 2 (Bitcoin): anchored in block 958695 (2026-07-19T07:37:00Z), 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/NLX9Z1800218.