Lobo may refer to: Places Lobo, Batangas, a municipality in the Philippines Lobo, Texas, a ghost town Lobo, Indonesia Lobo, Cameroon, a town in Cameroon Lobo Hill, near Belchite, Aragon, Spain Lobo,
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 0x53d15746a0c8842819acef3198eabd85d259031705f9867a2acad53a41328c2a. Chain 2 (Bitcoin): anchored in block 954134 (2026-06-17T19:41:05Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/7ee9e0be-65c1-4880-aa51-aeef1f1c38a2.json and https://artists.proofprofile.net/proofs/artist/7ee9e0be-65c1-4880-aa51-aeef1f1c38a2.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 0x46c07244e1eb7b044b659623bc6754ea25b95c11ac82d8a14eb47b5542580821. Chain 2 (Bitcoin): anchored in block 958913 (2026-07-20T16:58:47Z), 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/QZDFP1947451.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xd5b1792b9f175b92a0cefe209561fe20e14a33b585688c1fe040e971f59b4449. Chain 2 (Bitcoin): anchored in block 959087 (2026-07-22T02:05:55Z), 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/QZDFP1952048.