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
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xcb9e496f378daf01fb627c7f282030803a99a10afef711bef10c5881a6c2b0fa. 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/b63e18ef-164b-4cdb-a8fe-370b5a6258c4.json and https://artists.proofprofile.net/proofs/artist/b63e18ef-164b-4cdb-a8fe-370b5a6258c4.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
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3b8e6e9f0830759da216ea01806209ddd5d7f0ead7270a528d8114cebf8abab2. Chain 2 (Bitcoin): anchored in block 956484 (2026-07-03T10:47:44Z), 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/RUB422502902.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x09c154fb4129ea0fcb5305b1c1212384cafa1ddd82d6c5817729f9f3fd21e28d. Chain 2 (Bitcoin): anchored in block 958905 (2026-07-20T16:14: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/RUB422503001.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x8437d8cada3326946775004d835af5a176222e3626c959ed5849ab38cf9f60da. 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/RUB422201896.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xae7658e832c96e0e4036fb0f28f8f6e46e69c3c6380271f5089645c81d7b4643. Chain 2 (Bitcoin): anchored in block 956312 (2026-07-02T05:09:12Z), 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/RUB422201194.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x46881a0aec7c0046df2583630ae052d1264bdcfaa909c9ec4bc86a33c3249c4e. Chain 2 (Bitcoin): anchored in block 960473 (2026-07-31T22:27:44Z), 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/RUB422201898.
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