Laja may refer to: Bolivia Laja Municipality, a subdivision of La Paz Department Laja, Bolivia, a town in the municipality Chile Laja, Chile, a town in Bío-Bío Province Laja Lake Laja Falls Isla d
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 0x5ecbddcbb39827a992c0f4f6ac303cd48797306d0419a3a30e578e32569d92d8. Chain 2 (Bitcoin): anchored in block 954623 (2026-06-20T23:40:06Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/cbc4118e-706c-4f19-896e-fbde51d39859.json and https://artists.proofprofile.net/proofs/artist/cbc4118e-706c-4f19-896e-fbde51d39859.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 0x3c86031b5c3fb837802224367f17304a9585361f9646e90be69763a61b39bdf1. Chain 2 (Bitcoin): anchored in block 956856 (2026-07-06T01:25:57Z), 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/QZFZ62590083.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb05d5ceefcf3c47b77183896395a6ee6612271b2fce576dd9efbbbc604292441. Chain 2 (Bitcoin): anchored in block 956474 (2026-07-03T08:56:35Z), 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/QZFZ62590084.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3eefa6953a2b2624fc20eb16cce33754b9f2927ed910599e4fccedff049608ea. Chain 2 (Bitcoin): anchored in block 959128 (2026-07-22T12:33: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/QZDA42559401.