Lucky Me or LuckyMe may refer to: Music LuckyMe (record label) Lucky Me (album), a 2020 album by Killing the Dream Lucky Me, a 2001 album by Lucky Luciano Lucky Me (EP), a 2002 EP by Duke Specia
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 0x6225254ed35bd151d80aa38905cfd0f064e4c5fbbba0330e0d978222fa357f49. Chain 2 (Bitcoin): anchored in block 954667 (2026-06-21T07:29:20Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/afd36564-60d9-4701-b0aa-6fe97493c9f3.json and https://artists.proofprofile.net/proofs/artist/afd36564-60d9-4701-b0aa-6fe97493c9f3.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 0x362a3b6f8511064118d4b124632ba5b4e7ee23fb35aea99f3bc4181a3df62a61. Chain 2 (Bitcoin): anchored in block 959069 (2026-07-21T22:32:59Z), 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/GXD7V2474676.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x7210d3768fd7a9d854acc5a6af7cd32cf442d0276462b7bbcd8b60c7cc5ada62. Chain 2 (Bitcoin): anchored in block 956889 (2026-07-06T06:56:49Z), 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/AEA3A2497482.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x59ec631d5d4c38b5623c63d06f850c0c9c917c07cfbbccee23a36842e6503045. 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/SGW502262283.