CustodyStress
Archive › Multisig quorum failure
Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-00542

Multisig quorum failure — exchange custody (2018)

Constrained
Case description
A June 2018 case describes a DAO-structured investment vehicle whose Bitcoin treasury required token holder votes to release funds. During a governance attack, a malicious actor acquired enough governance tokens to pass a treasury-draining proposal. The multisig requirement limited the immediate damage but the attacker's vote could not be reversed.
Custody context
Stress conditionMultisig quorum failure
Custody systemExchange custody
OutcomeConstrained
DocumentationUnknown
Year observed2018
CountryUnknown
Structural dependencies observed
Institutional cooperation requiredThird-party platform dependency
What this illustrates
Getting access back required help from an institution — and that help wasn't available. Whether full access was ultimately possible is unclear, but significant delay or outside intervention was involved.
Outcome interpretation
Access remained possible, but only with delay, dependence, or significant difficulty.
Source
Publicly Reported
Evidence type
Forum post
Related cases involving multisig quorum failure
77 cases involve multisig quorum failure 512 cases involve exchange custody View archive statistics →
This archive documents observed custody survivability failures. It does not attempt to document all Bitcoin losses or security incidents. Submit a case
← All cases
Framework references
Terms guide
Survives
Access remained possible under the reported conditions.
Constrained
Access remained possible, but only with delay, dependence, or significant difficulty.
Blocked
Access was not possible under the reported conditions.
Indeterminate
There was not enough information to determine the outcome.
Single-person knowledge
Recovery depended on information or capability held by one individual who was unavailable.
Institutional dependence
Recovery depended on a third-party institution or service that was inaccessible or uncooperative.
Documentation gap
Recovery depended on instructions that were missing, incomplete, or unclear.
Authority mismatch
The person with legal authority to act did not have operational access, or vice versa.
Original text
Rate this translation
Your feedback will be used to help improve Google Translate