Tape or Tapes may refer to: Material Tape is long, narrow, thin strip of material usually used to stick things together. (see also Ribbon (disambiguation): Adhesive tapes Adhesive tape, any of many
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 0x8ce14a6680c08b29219fb2007661657e1a1c56558e22e69484ef8a6726571420. Chain 2 (Bitcoin): anchored in block 953909 (2026-06-16T07:53:13Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/183bf114-0b29-458f-8af0-1751aece0317.json and https://artists.proofprofile.net/proofs/artist/183bf114-0b29-458f-8af0-1751aece0317.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 0x38afde8585c728235a5ae40289f243001bf8bb6574dea7fc2a5c981a9d3638c9. Chain 2 (Bitcoin): anchored in block 959123 (2026-07-22T11:35:32Z), 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/TCAJE2597270.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x4f5e7e122124f2066e43bbc6ebf87d6657f81cb79c0056c50cffd25cdeec184f. 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/TCAJQ2500351.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xaf366d30356f99296b63ce5c490b52007e54eb9856cf6001fc57e7b9cb40798d. Chain 2 (Bitcoin): anchored in block 958857 (2026-07-20T09:45:25Z), 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/TCAJU2589331.