Cinder or Cinders may refer to: In general Ember, also called cinder Ash, also called cinder Scoria, or cinder, a type of volcanic rock In computing Cinder (programming library), a C++ programming l
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 0xf96eb8cf5121f01aff46f6beeb4f4c92db26107f846c76968bf1584e6ee1b966. 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/d1b2df25-f1a0-403b-843d-20d49649836b.json and https://artists.proofprofile.net/proofs/artist/d1b2df25-f1a0-403b-843d-20d49649836b.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 0xc52d599018659529ec019ccd7fbd2608434f1485f53d6aa069b4c9b546a821c2. Chain 2 (Bitcoin): anchored in block 956474 (2026-07-03T08:56:35Z), 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/TCAAY1134633.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x7df3c6499ef6991e149baf6f4d5a21740a3c74c83a7cbe44433bfda6518158e5. Chain 2 (Bitcoin): anchored in block 958224 (2026-07-16T02:28:43Z), 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/QMEU31907405.