Leaman may refer to: Leaman (surname) Leaman, Alberta, also known as Yellowhead County, Alberta, a municipal district in west central Alberta, Canada Leaman Place, Pennsylvania, a named place in Lanc
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 0x5b160901796710edd75e10c32c0000bc87bb063c0dbd218ce39b7a2072004034. Chain 2 (Bitcoin): anchored in block 953896 (2026-06-16T06:05:56Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/10289892-f9df-46fb-b46d-eaca9f737d91.json and https://artists.proofprofile.net/proofs/artist/10289892-f9df-46fb-b46d-eaca9f737d91.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 0x6d1cfa0ec94bfd39cdb2d0f344d6e61d72ab5549e013d9ea988b30ce896dfd6f. Chain 2 (Bitcoin): anchored in block 960284 (2026-07-30T17:23:26Z), 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/US83Z1790869.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa768edfcb7edb7c91d4c15c4fcc302daf585eba6c12b947af687b016115a7a3b. Chain 2 (Bitcoin): anchored in block 960105 (2026-07-29T12:35:17Z), 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/GBLV62317652.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x5ebc95ce40b831e9b60d34fcd74235ce177f75e09df92ecf5819ff210fef8ae1. Chain 2 (Bitcoin): anchored in block 958300 (2026-07-16T16:14: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/NLHR22500805.