Ily or ILY may refer to: ILY sign, an informal sign in American Sign Language for "I love you" Iły, Kuyavian-Pomeranian Voivodeship, Poland Iły, Masovian Voivodeship, Poland Islay Airport, Scotland (
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 0xb3b159ff35a9312ba1b75e6e41fa4a90f0aff80d96af46b2f31c05fc64457607. Chain 2 (Bitcoin): anchored in block 953407 (2026-06-12T19:24:56Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/56f7dc65-22c0-40bc-affe-a8376a617736.json and https://artists.proofprofile.net/proofs/artist/56f7dc65-22c0-40bc-affe-a8376a617736.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 0x83bb0dc3360b16caa27513daa8db42fe97d0f099acf239866efafd046a151e15. Chain 2 (Bitcoin): anchored in block 957891 (2026-07-13T18:21:04Z), 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/LBA0H1700214.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x765f38ebca7e69205d8c9fdea4fcb359dc9fe8936541dea4a44e3af0dc8f7dff. Chain 2 (Bitcoin): anchored in block 958256 (2026-07-16T07:22: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/LBA0H2001141.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xc580c6ac6b6172d6b2627b26da551e8d1850e3a5943a681721b1cf41efbebe6a. Chain 2 (Bitcoin): anchored in block 958733 (2026-07-19T12:51:21Z), 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/FR59R2154770.