Fuse or FUSE may refer to: Devices Fuse (electrical), a device used in electrical systems to protect against excessive current Fuse (automotive), a class of fuses for vehicles Fuse (hydraulic), a
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 0xf3ce062d9a62f4e752fd1d38483594e161a4892492568cca3b362e61ce4e1637. Chain 2 (Bitcoin): anchored in block 953660 (2026-06-14T17:20:01Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/5593cadb-abb6-46ee-b0cc-aec42871fca2.json and https://artists.proofprofile.net/proofs/artist/5593cadb-abb6-46ee-b0cc-aec42871fca2.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 0x30c34eef2c4ed2a751f6e1a4b841751f35a55e0e3e00dd02198e2d5e10d6ed18. Chain 2 (Bitcoin): anchored in block 957880 (2026-07-13T16:39:18Z), 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/UK4ZF1900058.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x220704cf187c856bf7d788b0f656c4184a13225a04e8d3aa5d7fa46f083f4137. Chain 2 (Bitcoin): anchored in block 958316 (2026-07-16T19:42:29Z), 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/UK4ZF2000010.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xaa7844b37e1887a18d23f2fde07727ce14cd442b7848b05fa2df01f86e4dcf31. Chain 2 (Bitcoin): anchored in block 953520 (2026-06-13T13:32:09Z), 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/GBDLM2100459.