Hoya may refer to: Places Hoya, Germany, a city in Lower Saxony, Germany County of Hoya, a former state in present Germany Hōya, Tokyo, now incorporated within Nishi-tokyo, Tokyo, Japan Hoya, Hpruso,
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 0x7e3f60ed651f0aa374ff0b495bb67c08579065114f854ea65227b9dcd423d717. Chain 2 (Bitcoin): anchored in block 953697 (2026-06-14T21:49:28Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/6440ecbf-815f-4695-a49b-b20552e00bb5.json and https://artists.proofprofile.net/proofs/artist/6440ecbf-815f-4695-a49b-b20552e00bb5.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 0x81bfa8848b8da33bbf1023b40bac5332f812714e3a705458a657146591f87102. Chain 2 (Bitcoin): anchored in block 957872 (2026-07-13T15:39:45Z), 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/KRB471800385.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x17bd5ffdb56e20cab0c0fd91cc9b0232bc669988afcbfdb52904dcd30ed56c14. Chain 2 (Bitcoin): anchored in block 958865 (2026-07-20T10:33:49Z), 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/KRB462300998.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x2b7211abefabf6bf4f24bede552fe063d16abc0e8646024a9802761dc0912ad6. Chain 2 (Bitcoin): anchored in block 953520 (2026-06-13T13:32: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/KRA491400487.