Tio may refer to: Tio (Zatch Bell!) a character from the Zatch Bell!, a Japanese manga series T'í'o, aka "Tiyo", a city in Eritrea Tio, Burkina Faso, a town in Burkina Faso Tió de Nadal, a chara
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 0xacd2ee3a42482f90b3fdf37d81bf885240dfc089135ae4a35df049019077e576. Chain 2 (Bitcoin): anchored in block 954065 (2026-06-17T08:10:43Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/558c8ba5-0a0f-4676-8e4e-0e77682f5822.json and https://artists.proofprofile.net/proofs/artist/558c8ba5-0a0f-4676-8e4e-0e77682f5822.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 0x8f9de2cc7d554ed0b8528831fac31bc5626f47d329e32391156ec586b762936a. Chain 2 (Bitcoin): anchored in block 958711 (2026-07-19T09:26:32Z), 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/AUP112000001.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb9af244a580aad49917886449ecc3b46a8d6e876e3de210b6da86bfe5b76b3e2. Chain 2 (Bitcoin): anchored in block 958208 (2026-07-15T22:40:25Z), 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/AUP112000003.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xc03f38fdeedaecc06b7728f8681bc17c9e6dfba9dd53218264c732bc45c113ac. Chain 2 (Bitcoin): anchored in block 958796 (2026-07-20T00:01:46Z), 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/AUP112000005.