Roye may refer to: Places France Roye, Haute-Saône, in the Haute-Saône department Roye, Somme, in the Somme department Canton of Roye, a canton in the department of the Somme Roye-sur-Matz, in
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 0x34627c00d2f13b73b2c2894b2f2e8c8ac4ab6e14c808bf26d1fe2f9811fd3801. 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/caa37392-7060-40be-8871-d2292b893c86.json and https://artists.proofprofile.net/proofs/artist/caa37392-7060-40be-8871-d2292b893c86.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 0x668ee8cd7e193301e0267cbdf9e3c428fb0d4b0f9978227096cf6f8c655957b7. Chain 2 (Bitcoin): anchored in block 960138 (2026-07-29T19:35: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/QZWDE2396554.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x8248d0a1dd5b322e7564debe71078a53a907e8434516bee9a6ff5f9bbea85104. Chain 2 (Bitcoin): anchored in block 960455 (2026-07-31T19:53:13Z), 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/NLD682202454.