Connect a wallet
The app can work with different wallet sources. A connected source may provide Solana transaction signing, Quorum packet signing, or both.
Wallet source types
| Source | What it can do |
|---|---|
| Quorum embedded wallet | Manage Quorum identities, register PQ keys, sign packets, and pay fees when an Ed25519 fee-payer identity is available. |
| Quorum extension | Provide the same class of Quorum signing features from a browser extension surface. |
| Standard Solana wallet | Pay transaction fees and sign ordinary Solana transactions. It does not automatically provide Falcon or Winternitz signing. |
Fee payer versus member authority
The fee payer submits a Solana transaction. The member authority approves a Quorum action. These can be different identities.
Relayer-friendly by design
A non-member fee payer can submit a proposal or vote transaction if the instruction includes valid member authorization.
When to switch wallets
Switch wallet source when:
- You need a different fee payer.
- The selected source cannot sign the required member scheme.
- A proposal requires a Falcon or Winternitz approval and the current wallet has only classical identities.
- You are testing how relayers or sponsored transactions behave.
Common connection states
- Disconnected: the app can show public information but cannot submit signed actions.
- Solana-only: the app can pay fees but needs another source for Quorum packet signatures.
- Quorum-capable: the app can supply one or more scheme-specific member signatures.
Wallet connect docs
Learn what the wallet exposes to apps and how requests are approved.