Blu or BLU may refer to: Businesses and brands Blu (Italian company), a telecommunications company Blu Manga, an imprint of Tokyopop blu eCigs, a brand of electronic cigarette owned by Imperial Tobac
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 0x5291e0f62002c5ffb9adf8e297893bd3af46a0fafc7e7f312f383a59f3f23a18. Chain 2 (Bitcoin): anchored in block 954784 (2026-06-22T02:53:59Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/f04ae2a6-19ff-4677-ba65-8e1cb596a55d.json and https://artists.proofprofile.net/proofs/artist/f04ae2a6-19ff-4677-ba65-8e1cb596a55d.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 0xed3523aae3884e09b5758295a0f9cf04ed35c3a63fd1ebc2e92ed1cddaced5da. 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/QZNWU2495218.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb64baed1d63da3ab2a061a4ba3b2f9930422e45eba87d1500c462f81aecd03af. 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/QZTAS2560569.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x755a6eb7c0b26254d1ad7b4bd239b4497d3c046b0add91a801da8751fe7d2884. Chain 2 (Bitcoin): anchored in block 956634 (2026-07-04T10:04:33Z), 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/MNA032500238.