Léo is a proper noun in French, meaning "lion". Its etymological root lies in the Latin word Leo. Léo is used as a diminutive or variant of the names Léon, Léonard, Léonardon, Leonardo, Léonid, Léono
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 0x3521998512bc4a84f2f38e24a97bb274e8ca81069bcab6a3180e280d66c98448. Chain 2 (Bitcoin): anchored in block 954587 (2026-06-20T19:10:41Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/b87abcbd-42ca-45b7-b4f6-0923feca4446.json and https://artists.proofprofile.net/proofs/artist/b87abcbd-42ca-45b7-b4f6-0923feca4446.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 0x40ff4364e0adfa8a9f4990b4dc72382d0f58a71158f40587d0e46c11935f94c6. Chain 2 (Bitcoin): anchored in block 960441 (2026-07-31T17:29:52Z), 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/QZHZ42017456.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xe048738a4693f4685e2a78e0b28315ab29c47db9ac2c3b4082da060d73167933. Chain 2 (Bitcoin): anchored in block 960317 (2026-07-30T21:35:24Z), 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/QZHZ42017459.