Ledu may refer to: Ledu District, Haidong, Qinghai, China Ledu (prince) (1636–1655), Prince Min of the Second Rank of the Qing dynasty See also Leduc (disambiguation)
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 0x9fd5cae31c5f9d8d698f6aef25d05e60886aa7b2b846adafae0728b10a548dce. 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/db214741-9c42-4ae7-bbc5-67f1de271f27.json and https://artists.proofprofile.net/proofs/artist/db214741-9c42-4ae7-bbc5-67f1de271f27.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 0xb312055cae3e0395023ac2b690d8df5f83f0067fa8b7ca0e5d150ec764662875. Chain 2 (Bitcoin): anchored in block 956545 (2026-07-03T19:59:51Z), 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/DEA622302398.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3b9fe09d161060a24d314234872a64e04f0876518ae47d01ef6ba22117707603. Chain 2 (Bitcoin): anchored in block 959015 (2026-07-21T13:52:01Z), 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/DEA622402127.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xe3ce6d16ed819295c55f5df86e025a144cd5f2b42814cbefa5e47511be3efec5. Chain 2 (Bitcoin): anchored in block 958905 (2026-07-20T16:14:34Z), 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/DEA622503583.