We have a multisig.
Who holds the keys, what the signers see, what a multisig may change, and how to check one for any token.
Safe, they said · 3/10
Created by:
Legendary Klack
Tags:
"We have a multisig" is the answer most projects give when you ask who controls the money.
It sounds like the end of the question. It is the start of it.
This is part three of our series "Safe, they said." Ten sentences that projects use to calm you down, one a week. Here is the third one, taken apart.
What a multisig is, in one paragraph
A multisig is a wallet that needs more than one key to move anything. "Three of five" means five people hold a key, and any three of them have to sign. One lost or stolen key is not enough to empty it.
That is a real improvement over a single key. It answers one question: what happens if one person makes a mistake or disappears? It does not answer the others.
Question one: whose keys?
Five keys on five laptops in the same team, the same office and the same chat are closer to one key than to five. They share the same habits, the same software and the same people who might trick them.
In July 2026 a cross-chain bridge of the trading platform AFX lost about $24 million, by the count of the security firm Halborn. Its transfers needed two thirds of the votes of seven validators. The attacker held the keys of five of them. The contract checked the signatures, found them valid, and paid out.
The code did exactly what it was built to do. The threshold was met by the wrong people.
Question two: what did the signers see?
A signer approves what the screen shows. In February 2025 the exchange Bybit lost about $1.5 billion from a multisig wallet. According to the forensic firms involved and to Safe, the provider of the wallet software, attackers had replaced code on the wallet's website and proposed a disguised transaction. The signers approved what looked like a routine transfer.
More signers do not help if all of them look at the same manipulated screen.
Question three: what can the multisig change?
This is the question that is asked least.
A multisig that holds funds is a custodian. A multisig that can also change the rules, upgrade the contracts or redirect where the money goes is a small committee with the final word. "We have a multisig" says nothing about which of the two it is.
Question four: is there time to say no?
If a decision takes effect the moment the last key signs, nobody can stop a bad one. A delay between signing and execution, a timelock, gives everyone else time to see it coming and react. The AFX bridge had a dispute window of 200 seconds.
How to check it for any token
You do not need to trust a website for this, including ours.
- Find the multisig's address. It should be published, and it can be opened in any block explorer.
- Read the threshold and the number of signers there, not on the project's website.
- Ask who the signers are, and whether they are independent of each other.
- Look at what the multisig is allowed to do: hold funds, or also upgrade contracts and change rules.
- Look for a delay before execution, and for who can stop a transaction in that time.
Where SHIBC stands
The SHIBC token contract has no owner. Its ownership was renounced in November 2024, so there is no key, single or shared, that can change it.
The DAO's settings are guarded the same way. Only the DAO itself may change its voting rules or upgrade its voting plugin. The person maintaining the project holds no special role there. Anyone can read these permissions on chain, and our whitepaper lists them in section 6.6.
For the parts that will hold value, the plan is written down in section 7.4 of the whitepaper: a multisig as custodian of keys, with a threshold that survives the loss of one key holder. And one rule that does not bend: the multisig holds keys, it does not change the rules the DAO sets.
What we take from it
A multisig is a good lock. Whether it protects you depends on who holds the keys, what they see when they sign, what the lock is allowed to open, and whether anyone has time to say no.
Our view of how a token should be run: Custodian, yes. Override, no. Publish the address, the threshold and the signers. And give everyone else time to object before anything happens.
Next week, part four: "The community decides."