Search Quorum docs

Search pages and sections across all documentation sets.

Technical docs

a step-by-step guide

Key derivation

How Quorum separates derived identities from one BIP-39 mnemonic.

Key derivation

The wallet can derive multiple scheme identities from one mnemonic while keeping each scheme on a separated path.

Quorum is devnet software and should not be used to protect production funds before audit and mainnet readiness.

Separation model

Each scheme uses distinct derivation context so signatures cannot be replayed across identity families.

This separation means compromise of one derived classical identity should not automatically reveal a Falcon or Winternitz derived identity. It does not make the root mnemonic quantum-safe, and it does not reduce the need to protect backups.

Mnemonic risk

The mnemonic remains the root secret. Anyone who obtains it can derive the identities that the wallet supports, including future signer schemes added to the same wallet.

Operational guidance

  • Treat mnemonic backup as the authority root.
  • Rotate member identities through settings proposals.
  • Use test-only mnemonics in demos and local environments.
  • Document which derived identity is registered for each multisig member.
Derivation boundary

Separate derivation branches reduce cross-scheme blast radius. They do not turn a compromised mnemonic into a safe secret.

Wallet key derivation model

Read the wallet-facing version of this model.