thumb|Flames of charcoal A flame () is the visible, gaseous part of a fire. It is caused by a highly exothermic chemical reaction made in a thin zone. When flames are hot enough to have ionized gaseo
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 0xe48c420eb48d56623441ca5e938ddea228a5cdf1b02bacedda2984fc74b285ec. 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/15c78c63-36a9-41d2-8f0b-da4e0bfc79d3.json and https://artists.proofprofile.net/proofs/artist/15c78c63-36a9-41d2-8f0b-da4e0bfc79d3.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
U Hodnicima Vremena, Vol. 2 (Flame.LMR.Edition)
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 0x5e9f12539fa1e995eb821db62a2b8a14214d00268b7deb5db9fc2680506f767c. Chain 2 (Bitcoin): anchored in block 960441 (2026-07-31T17:29:52Z), 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/RSA221600080.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x0f2a9a88a631c92e68f42b3644f3733d537c21999f5e7a9fe6ac86065c05092b. Chain 2 (Bitcoin): anchored in block 960506 (2026-08-01T03:50: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/RSA221601120.