Lune may refer to: Rivers River Lune, in Lancashire and Cumbria, England River Lune, Durham, in County Durham, England Lune (Weser), a 43 km-long tributary of the Weser in Germany Lune River (Tasmani
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 0x4633abd29a864fa34c42d265b0c3d5df375c0f2970d78c1b780c04ca3269ea7e. Chain 2 (Bitcoin): anchored in block 954058 (2026-06-17T06:34:31Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/44c3c718-7577-49cc-a43d-fcb5b40dd649.json and https://artists.proofprofile.net/proofs/artist/44c3c718-7577-49cc-a43d-fcb5b40dd649.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 0x3448358c8bc4acf648e8848783240b88756ca30bae93940e714ebe149f63bc75. Chain 2 (Bitcoin): anchored in block 958775 (2026-07-19T20:13:58Z), 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/KRB922000773.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x158fdc6a859a6dab034a80b480193da6faf0ab43932cb95ee21355857c7b9219. Chain 2 (Bitcoin): anchored in block 959107 (2026-07-22T07:19:23Z), 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/KRA341318116.