In military munitions, a fuze (sometimes spelled fuse) is the part of the device that initiates its function. In some applications, such as torpedoes, a fuze may be identified by function as the explo
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 0x20c0d92e87dcb0de8f3f8f38d543bf5d8d3e64e46796164e9e548368e1a2b10a. 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/c66afdbe-7b06-4a50-8ae4-7ceec2412397.json and https://artists.proofprofile.net/proofs/artist/c66afdbe-7b06-4a50-8ae4-7ceec2412397.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 0x597eefbf586f38cadd39df8f67c39aa78704e8bab2536db22614b71cd29a3a86. Chain 2 (Bitcoin): anchored in block 959123 (2026-07-22T11:35:32Z), 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/PLC062524951.
Recepta Na Sukces (Ale To Sroga Vixa) [REMIX]
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x0147776c4344b884d2cf98e81fea1feb0c6eb065c0c2cea805184457fc3f6a48. Chain 2 (Bitcoin): anchored in block 956420 (2026-07-03T00:42:11Z), 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/PLC062543405.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x79cfcc64fcc497cd95e2dbef608171972a6ac66a3defc8d5aa19ecfc3bc6ce54. Chain 2 (Bitcoin): anchored in block 956634 (2026-07-04T10:04:33Z), 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/LVM002500081.