Belo may refer to: Organizations Belo Corporation, known as A. H. Belo Corporation from 1926-2000, a United States media company now part of Tegna Inc. DallasNews Corporation, known as A. H. Belo C
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 0xdcc794fd1731389fadf238ed39ffb75a632f4c2214f87b452225e909ba3f0dcf. Chain 2 (Bitcoin): anchored in block 953777 (2026-06-15T11:52:51Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/ce0a7d25-3b9b-4d48-80be-2414603fe3db.json and https://artists.proofprofile.net/proofs/artist/ce0a7d25-3b9b-4d48-80be-2414603fe3db.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 0xd4f2c53714a2a80e25497bd44a8eec6d7421b0dc8ecce9bdc409e6767778bec2. Chain 2 (Bitcoin): anchored in block 956822 (2026-07-05T18:48:28Z), 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/ES71G2026401.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xc258a09e0955ce7834e0c5949cfdfe9b18532e6e4fb25839ec7e8233455c070d. Chain 2 (Bitcoin): anchored in block 958194 (2026-07-15T20:32:27Z), 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/QZZ7S2482409.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x531b930ac39b7106f006c9469b94358ff188ff91a48e6c419920d130ab575106. Chain 2 (Bitcoin): anchored in block 957882 (2026-07-13T16:48:10Z), 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/QZHN72502189.