Lia or LIA may refer to: Places Lia, Iran, a village in Dashtabi-ye Sharqi Rural District, Dashtabi District, Buin Zahra County, Qazvin Province, Iran Lia, Norway, a village in Sør-Fron municipalit
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 0xbb0c91d2e96944704b82b43a17e03b97ac93f978c633cee8d8b2d916cc76c701. Chain 2 (Bitcoin): anchored in block 954638 (2026-06-21T03:45:44Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/d41ef29f-df87-428d-a265-328f86e4b733.json and https://artists.proofprofile.net/proofs/artist/d41ef29f-df87-428d-a265-328f86e4b733.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 0x013274d6db3fb83a814255f68efacc7c71a2a0a01b6a573f0f0ee030ec2a99f8. Chain 2 (Bitcoin): anchored in block 958319 (2026-07-16T20:12: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/SEYOK2415994.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xf835eb84c5be1a0cd3d27649ee980064e98ba1edec38b7a1856ffa26f5b79c82. Chain 2 (Bitcoin): anchored in block 958111 (2026-07-15T06:58:20Z), 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/SEYOK2519865.