>_ DigitalGuards
← all posts
2026-11-12 qrlqrl-2.0quantavaultmultisigpost-quantum

QuantaVault: an early look at a post-quantum multisig for QRL 2.0

QuantaVault is a shared vault for QRL 2.0. Several owners hold it together, and the vault itself verifies each of their ML-DSA-87 signatures on chain. It is early work on the test network.

QuantaVault is early work on the QRL 2.0 test network. It has not had an independent security review yet and is not ready for real funds. Treat everything below as a preview.

Last month the QRL core team merged our ML-DSA-87 verification precompile into the QRL 2.0 client. In the post about it we listed what it makes possible, and a multisig came first. QuantaVault is that multisig: a shared vault for QRL 2.0 that several owners control together. A first look is at quantavault.io.

What it is

A vault has a list of owners and a threshold, for example two of three. Everything the vault does, from sending Quanta to changing its own owners, needs that many approvals. A single key cannot move the funds, and with two of three a lost key leaves the vault usable.

That makes it a fit for anything one person should not control alone: a team treasury, a project’s funds, or the administrative powers of a smart contract.

Post-quantum approvals, checked on chain

Each owner approves by signing the transaction with ML-DSA-87, the signature scheme every QRL 2.0 account uses. The vault counts those approvals itself. When the transaction is executed, the contract verifies every signature through the ML-DSA-87 precompile and only then acts.

Owners sign typed data in the QRL-SIGN-TYPED-v2 format, the same format MyQRLWallet already signs, so a request arrives as named fields. Every transaction also carries a deadline, after which it can no longer run.

Built on Safe

QuantaVault is a port of Safe Smart Account v1.5.0, one of the most widely used multisigs on Ethereum, to Hyperion, the contract language of QRL 2.0. Safe has secured assets on Ethereum for years, and we wanted that design as the starting point.

The port follows the Safe sources file by file, and every difference is written down. The main ones come from the chain itself: QRL 2.0 uses 64-byte words and addresses, derives contract addresses in its own way, and signs with ML-DSA-87 where Ethereum uses ECDSA.

More than a wallet

Two additions come with it:

  • A timelock can hold an approved action for a set time before it runs, so a change to something important is visible before it takes effect.
  • A proposal log on chain lets owners find what is waiting for their signature, with no central server in between.

With those, a vault can hold more than funds. Our first use will be our own: the administrative roles of the QRL Name Service contracts are planned to move to a vault, so that no single key controls the names.

How it is checked

A multisig is only worth using when its contracts deserve trust, so most of the work so far went into checking them:

  • test suites that run against both code generators of the Hyperion compiler;
  • a fuzzer that compares the contracts, step by step, with an independent model of the vault;
  • formal proofs of core rules, for example that only the vault itself can change its owners and its threshold;
  • two internal security reviews. The latest found no way for fewer than the required owners to authorise a transaction.

An independent review by an outside party is still to come. It comes before any vault holds real value, which is why QuantaVault stays on the test network for now.

Where it stands

  • The contracts are deployed on the QRL 2.0 test network.
  • A web app creates a vault, collects the owners’ signatures and executes. It is in internal testing.
  • The source code is private during this early phase and will be published before any use on mainnet.

What comes next

An independent security review and a public test version of the app. We will write again when there is something to try.

Questions and feedback are welcome through the contact form.

← more from the blog work with us