Governance
Who decides what.
Twine launches under a multisig. STRAND token voting goes live after the protocol has earned the right to it - an external audit and a clean stretch on mainnet. The transition is built in from day one; no contract redeploy is required to hand control over.
Today
A multisig controls the protocol's admin surface. The signers can authorize new pools, re-tune live pool parameters, pause the hook in an emergency, and resolve a structural break once the underlying market has reconverged. The multisig cannot seize user funds, alter LP balances, or change vault staker positions - those rules are enforced by the contracts themselves.
Tomorrow
STRAND voting will replace the multisig as soon as the protocol clears a Tier-1 audit and accumulates a meaningful soak period on mainnet. The intended parameters mirror the spec: a proposal threshold of 1% of supply, a 5% quorum, a two-day voting window, and a two-day timelock before any approved change takes effect.
Voting will live here, on this page, embedded from Tally. Until then we keep the multisig in place rather than ship a token-voting layer that hasn't been audited alongside everything else.
Vote
On-chain voting
Comes online after audit + mainnet soak.
When live, this will be a Tally embed reading directly from the v2 Governor.
What can't change, ever
- Twine never custodies user assets - they live in Uniswap v4's PoolManager and the per-pool vault contract.
- Governance cannot move LP positions or vault stakes between accounts.
- Governance cannot mint MSTRX or any other tokenized equity - those are issued by their respective wrappers (Backed, Ondo, Dinari), not by Twine.
- The asymmetric-fee mechanic and the structural-break drawdown rules are coded into the hook; the multisig can pause them, not rewrite them.