Riet or RIET may refer to: Riet, Germany, a village in Baden-Württemberg, Germany Riet, Switzerland, a settlement in the municipality of Neftenbach in the Swiss canton of Zürich Rajasthan Institute o
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 0xb58fa18f3ec977c492005f6beef3465c405730ebd46f1524b18171f9406d78f0. Chain 2 (Bitcoin): anchored in block 954533 (2026-06-20T08:57:02Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/a68c1eee-20b8-4258-bc9f-cfdc4f8a8ee3.json and https://artists.proofprofile.net/proofs/artist/a68c1eee-20b8-4258-bc9f-cfdc4f8a8ee3.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 0x0a611d9d364e4602425f13cd2c7147808cbab8827634e42d8a1360a91fe2b8f9. Chain 2 (Bitcoin): anchored in block 956711 (2026-07-04T22:48: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/BEL032000045.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x0a611d9d364e4602425f13cd2c7147808cbab8827634e42d8a1360a91fe2b8f9. Chain 2 (Bitcoin): anchored in block 956375 (2026-07-02T16:51:38Z), 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/BEL032000045.