Scan, SCAN or Scanning may refer to: Science and technology Computing and electronics Graham scan, an algorithm for finding the convex hull of a set of points in the plane 3D scanning, of a real-wo
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 0xfa44836e917ecb3053b230c598e707f71440fafd01a6265c319dbaee9c696741. 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/2ef91ca9-8ae8-423c-b897-8c75559b6a28.json and https://artists.proofprofile.net/proofs/artist/2ef91ca9-8ae8-423c-b897-8c75559b6a28.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Cendikiawan Tak Mungkin Menyintai Seniman
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 0x61b628a667e7f9f9839000a897a3731d9ceedfe5b624704a71fd597e28b9c419. 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/MYUM70900711.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x988f556c302221c87586390bdcff78767765c2a2ecd927daaa8851e2146f9544. Chain 2 (Bitcoin): anchored in block 958708 (2026-07-19T09:08:25Z), 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/MYUM70901144.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa272e5bb38ee0b9e7b34152655d918cdce45a186419889cc318bd40e474fbef9. 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/MYUM70900706.