A bitstream (or bit stream), also known as binary sequence, is a sequence of bits. A bytestream is a sequence of bytes. Typically, each byte is an 8-bit quantity, and so the term octet stream is so
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 0x304a1412730e50371fcd40fd6c3fe5b3a04e99ae9a63d3c18262a0ce330b18ea. Chain 2 (Bitcoin): anchored in block 954623 (2026-06-20T23:40:06Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/caa5265e-98f8-4b50-9363-1f039017e421.json and https://artists.proofprofile.net/proofs/artist/caa5265e-98f8-4b50-9363-1f039017e421.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
A Pain That I'm Used To - Bitstream Threshold Mix
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 0x71c86f557e0e1118f8c39b2ac9935b854dc50ad643cd229ff4ed61836c3c69f1. Chain 2 (Bitcoin): anchored in block 960179 (2026-07-30T00:39:11Z), 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/GBAJH0502190.
A Pain That I'm Used To - Bitstream Spansule Mix
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xe9717b82e3a6e7bad74a89f84d06ba3f0e8ea9db00c7523ea95fbaf2bc6537a6. Chain 2 (Bitcoin): anchored in block 957043 (2026-07-07T13:52:39Z), 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/GBAJH0502191.