Backend
Release-Bound Withdrawal Authorization for Bitcoin Custody
arXiv cs.CR0 views
arXiv:2611.25231v1 Announce Type: new Abstract: A compromised cryptocurrency withdrawal backend can request signatures on unauthorized payments. Previously signed transactions may remain spendable after pause or become spendable again after a reorganization. Release-Bound Withdrawal Authorization (RBWA) orders permits against pause in a replicated journal and restores exposure when its closing evidence disappears from Bitcoin's active chain. An optional route delays large payouts and permits independent cold recovery. Direct payments confirm in one block on regtest, and staged payments confirm in three or seven at delays of two or six. After rollback, a replayed recovery can win or lose to an already exported mature payout. Authenticated receipts can revoke one signing lease in a shared wallet. In matched synthetic schedules, probes reduce permits through compromised leases from 20 to 9 out of 33, with one false fence. Two held-out HTTP workloads find equal fixed-threshold precision for boosted audit and probe-augmented detectors. The audit fields already expose the probe authentication outcome. Live tests verify an exact maintenance exception and add a file marker as a distinct source. The marker fences a compromised lease that RPC-only audit misses. Audit with the same file-read evidence also fences a reader who bypasses the probe. The results tie the benefit of active probing to which evidence the operator can obtain.
Source:https://arxiv.org/abs/2611.25231PreviousReject and Report: Forgery-Evident Undetectable Watermarks for Generative Image ModelsNextTRACE-5G: Trust-Aware Runtime Attestation and Continuous Enforcement for 5G User Equipment
Related posts
Splunk's Empty Cluster Secret Turns a Standalone Default into an Authentication Bypass
0dev.to
Pragmatic zero-trust: what to ship in the first 90 days
0dev.to
The EKS cost playbook: 7 levers we pull on every audit
0dev.to
Building a hearing test in the browser with the Web Audio API (and why we refuse to call it an audiogram)
0dev.to
How we score French speaking with AI: an honest look at limits
0dev.to
What a Four-Letter Word Ladder Taught Me About Planning Under Constraints
0dev.to