REA or Rea may refer to: Places Rea, Lombardy, in Italy Rea, Missouri, United States Rea River, in Fiordland, New Zealand River Rea, a river in Birmingham, England River Rea, Shropshire, a rive
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 0x1ba6ffc722090dd5852eaaf0e70c1628010f3d51a314f1d6a4384be02a7f6090. Chain 2 (Bitcoin): anchored in block 953903 (2026-06-16T07:05:05Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/13fa4e6a-9ccf-4b9f-ba5f-69ac5129bb31.json and https://artists.proofprofile.net/proofs/artist/13fa4e6a-9ccf-4b9f-ba5f-69ac5129bb31.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 0x28a724a4f73f44d2f862a77de13c6b44f64bd25bb9bb7ab3d97556cc631259a2. Chain 2 (Bitcoin): anchored in block 958816 (2026-07-20T03:51:05Z), 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/USCGH2410140.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x883021cc0905fcffc066ce2b260b889a1251523ab900a129c519a8743e712075. Chain 2 (Bitcoin): anchored in block 959002 (2026-07-21T11:47:29Z), 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/USCGH2410141.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xdedb14c6eed8669d025f6947a3cc1d1f3aff4cdda58851449891fb6a920b1039. Chain 2 (Bitcoin): anchored in block 958180 (2026-07-15T17:59:52Z), 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/USX9P2478040.