App overview
The Quorum app is the operating surface for mixed classical and post-quantum Solana multisigs. It helps a team create a multisig, register member identities, propose actions, collect approvals, execute approved work, and review the resulting on-chain history.
Quorum is devnet software. Do not use it to protect production funds until audit, mainnet deployment, and operational release guidance are complete.
What the app manages
- Multisigs: stable governed accounts with thresholds, permissions, and proposal counters.
- Vaults: Solana accounts controlled by the multisig.
- Members: Ed25519, Secp256k1, Falcon-512, or Winternitz identities.
- Proposals: transactions or settings changes waiting for approval.
- Approvals: scheme-specific signatures over canonical Quorum preimages.
- Execution: submission of approved actions after thresholds and timelocks are satisfied.
Main app areas
| Area | Use it for |
|---|---|
| Overview | Check multisig health, active proposals, vault context, and next actions. |
| Transactions | Review, approve, reject, cancel, or execute proposed vault actions. |
| Builder | Create governed Solana actions for the multisig to approve. |
| Assets | Inspect governed SOL and SPL token balances. |
| Members | Review identities, permissions, and signer coverage. |
| Settings | Propose threshold, timelock, member, and policy changes. |
| Programs | Govern upgrade buffers and program authority actions. |
| History | Review executed, cancelled, rejected, and unknown activity. |
How to read these docs
Use the App docs for day-to-day operation. Use Wallet docs when a question is about keys, identities, recovery, or signing prompts. Use Technical docs when a question is about program state, cryptography, or protocol invariants.
Create a test multisig and move through the basic propose, approve, execute loop.
Learn how the wallet supplies classical and post-quantum signer identities.
Mental model
The app does not make a transaction safe because a button was clicked. It makes an action executable only after the program verifies member authority and records enough valid approvals. The browser UI is a coordination layer; the on-chain program is the policy layer.