Lay or LAY may refer to: Places Lay Range, a subrange of mountains in British Columbia, Canada Lay, Loire, a French commune Lay (river), France Lay, Iran, a village Lay, Kansas, United States, an uni
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 0xc47bfd9a69a13127f49e9a5dfc1c33b3cf75cbd65b040a2052f45028b1d83fbb. Chain 2 (Bitcoin): anchored in block 953750 (2026-06-15T06:12:23Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/aa54df2c-b33a-4dea-a3f8-6fb2c7d0418d.json and https://artists.proofprofile.net/proofs/artist/aa54df2c-b33a-4dea-a3f8-6fb2c7d0418d.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 0x89d5ec422606c7886e6b1ae21c5d526f634624302ccef7e453e1d746e7581b69. 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/HKC371642271.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x75a1b7eeceaac9880109a6bd8c14c540e4c033610dc231010acb71ae4e946437. Chain 2 (Bitcoin): anchored in block 958415 (2026-07-17T12:50:13Z), 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/HKC371632026.