Picoquorum Launch app

Learn

Why a multisig, and why this console.

One seed phrase is one point of failure. A multisig takes it away: several owners, and nothing moves until enough of them approve. Picoquorum is a new kind of owner to put in one, a small console with its own screen and a key sealed in a chip.

The videos are on their way. Nine short explainers are written and none is recorded yet. Until one is up, its script is here to read.

Start here

Why a multisig, what one is, and what an approval looks like. No background needed.

  1. 1 · For everyone

    One seed phrase, one point of failure

    Twelve words on paper: copy them or lose them, and the money is gone. Why a multisig is the fix, and where a sealed hardware cosigner fits in one.

    Read the script
  2. 2 · New to crypto

    Two of three: a multisig in two minutes

    A shared account with more than one lock. Three people hold keys, any two approve, and no one acts alone. No jargon.

    Read the script
  3. 3 · For wallet users

    The multisig is the wallet

    A browser wallet, a phone app and a hardware wallet are three ways to hold a seed phrase. With a multisig, what you hold is one vote, and Picoquorum is built to be only that.

    Read the script
  4. 4 · The demo

    One approval, start to finish

    Propose, read every page, check the verify code with whoever proposed it, hold Sign for two seconds, execute. Let go early and nothing is signed.

    Read the script

The hardware

The board, zone by zone, and every way it can fail. Drawn on Mono, the board planned for developer kits.

  1. 5 · Technical

    Inside the console

    Three zones: the cable, which isn't trusted and can't send firmware; the console, which rebuilds the hash from the fields it shows; and the key, which signs it. And the lock that isn't on yet.

    Read the script
  2. 6 · Technical

    When the hardware fails

    It dies, it glitches, someone reflashes it, swaps the chip, cracks the chip or swaps the whole box. Each one costs the same thing: one vote out of several.

    Read the script

Being an owner

Getting a key, and what holding one asks of you, said plainly.

  1. 7 · Getting a key · the plan

    A new key, from the bench to your Safe

    The bench marks the chip and makes no key. Your console checks the mark, makes the key in front of you, and you seal it. Then: where funds go, and where they never should.

    Read the script
  2. 8 · For owners

    A key with no backup

    The key can't be copied. That is a feature and a bug: nothing to phish or photograph, and nothing to restore. The Safe's other owners are the backup.

    Read the script
  3. 9 · For owners

    What it protects, and what it doesn't

    It guards against a lying screen and a leaked secret. It doesn't guard itself: no PIN, no fingerprint. Keep it safe, notice fast when it's gone, and don't say where it is.

    Read the script

Don't want to wait?

Everything the videos will say is already written down.

  • See the hardware. Mono, the reference console: what it is, where it stands, and the boards it comes from.
  • Read the guide. The owner's guide goes from a board to a console that signs for your Safes.
  • Read what it can't do. The security model says what a sealed key doesn't protect you from.

How these are made

Each script is a file in the repository, next to the docs it draws on, with a list of the claims to check again before recording. If a video says something the docs don't, the docs win.

Experimental. Early design. Use a testnet first and small amounts on mainnet. The Safe's threshold is the real control.

All the scripts, and what's planned next · @picoquorum on X