Raha may refer to: Raha Assembly constituency of Assam, India Raha, Assam, a village in India Raha, Muna, capital of Muna Regency, Southeast Sulawesi, Indonesia Raha, Nepal, a village in Dolpa distr
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 0x88a1d04eb12c85fd44545b331f0c73c177428252121a69bbfebe37de059a6631. Chain 2 (Bitcoin): anchored in block 954066 (2026-06-17T08:11:48Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/71530e67-0a49-4118-846e-27614a0a898b.json and https://artists.proofprofile.net/proofs/artist/71530e67-0a49-4118-846e-27614a0a898b.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 0x1f38f48a20b86dd3057d8a96803bc7f115ad1efc2ede5b3e127f32c084428ca1. Chain 2 (Bitcoin): anchored in block 957118 (2026-07-08T03:20:19Z), 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/GB9PM1400262.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xcf7f30e386ae26b14e450e179006eef37029f8f3eac939c7013b3e2f78535ba3. Chain 2 (Bitcoin): anchored in block 956302 (2026-07-02T03:30:09Z), 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/GB9PM1400263.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x874cc6f1e979059aa11cfa9aef6b1b6732eceec2eff7ed90ae287cec7287e515. Chain 2 (Bitcoin): anchored in block 960327 (2026-07-31T00:26:26Z), 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/GB9PM1400261.