LGZ or lgz may refer to: LGZ, the IATA code for Shannan Lhünzê Airport, Tibet, China lgz, the ISO 639-3 code for Gendza language, Democratic Republic of the Congo
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 0x67d748a3af4ce4b8f30cdb33e8c138ff63ca80d30c706aca3dd9b838273c4115. Chain 2 (Bitcoin): anchored in block 954342 (2026-06-19T03:22:39Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/8e620e5f-2309-4a6c-ada7-5cb93ab2c4b9.json and https://artists.proofprofile.net/proofs/artist/8e620e5f-2309-4a6c-ada7-5cb93ab2c4b9.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 0x26af16afa103ee11ab363cca91ecccede0dad1a593cf8a4ba93b56f5badcd5f8. Chain 2 (Bitcoin): anchored in block 958761 (2026-07-19T17:49:48Z), 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/SE6SA2421091.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x1f57a5ca89fc3977810328ce2d80d79662fc6ac2ea89eb964e848908b7636afc. Chain 2 (Bitcoin): anchored in block 956551 (2026-07-03T21:18:05Z), 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/SE6XY2505632.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3e0b2eed13f207ff2745ab54ea32d09db93fede825bc19ac043dfbbd4a15d1ee. Chain 2 (Bitcoin): anchored in block 958531 (2026-07-18T09:39:18Z), 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/SE6XX2584371.