Hondo may refer to: Places Rio Hondo (disambiguation), the name of several locations, derived from the Spanish word for "deep" Canada Hondo, Alberta, an unincorporated community Japan Hond
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 0x7e6d63d89540b9ac1aee7873de0fd6b3c81d1974b254da174b86e6e103184ba2. Chain 2 (Bitcoin): anchored in block 953791 (2026-06-15T13:40:30Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/dceffce2-3040-4bd9-8a9f-214c3abf6ccb.json and https://artists.proofprofile.net/proofs/artist/dceffce2-3040-4bd9-8a9f-214c3abf6ccb.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 0x3f91215ba318a2bd8bf2344e43a6fd5e16b2b1c8db4d23433f432aacc6856d8d. Chain 2 (Bitcoin): anchored in block 958058 (2026-07-14T20:20: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/QZFZ21902855.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x8ccc01a25ac87a7e71740bd730d02f62e58baac2bfa15b192d80a241f3fa3973. Chain 2 (Bitcoin): anchored in block 956856 (2026-07-06T01:25:57Z), 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/FRX452036831.