Picoquorum Launch app
New Mono, the reference console

Hardware approvals for Safe

Several people, several keys, one Safe.

Picoquorum is a small device that is one owner of a Safe multisig. It shows what a transaction does on its own screen, works out the hash itself, and signs with a key that never leaves its chip, only when you hold Sign.

Have a Safe already? The app opens it, checks every confirmation in your browser, and executes. It holds no key.

Mono in its case, standing on its dock: a small dark bar with a screen at the top showing Send 0.05 ETH, and three buttons under it, red, white and green.
Mono in its case, on its dock. A drawing of the design: nothing is built yet.

The hardware

Mono, the reference console

Mono is the device Picoquorum is working toward, and the one the rest is measured against. Today it is a design: written by a script, routed and checked, not ordered and not built. Mono is a working name.

  • A screen and three buttons. Reject, Next and Sign, in a row under a 1.14″ screen. Reject is red and takes one press. Sign is green and has to be held.
  • The key is on the board. A secure element, soldered on. Its private key is made inside the chip, and no command reads it out. There is no seed phrase.
  • No radio. No Wi-Fi and no Bluetooth on the board. Its USB-C reaches a serial chip and nothing else: a computer passes on Safe's queue, and has no say in what gets signed.
  • Open hardware. An RP2350 on a 40 × 89.5 mm board, laid out for JLCPCB to assemble, with the screen clipped in by hand. The files to make one are in the repository.
Mono's board: the screen at the top, D0, D1 and D2 in a row under it, the key chips' sites below them, the RP2350 in the middle, and the USB-C at the bottom end.
The routed board, as KiCad draws it. The screen is a box.

The firmware runs today on a dev console you can build for about $35 with no soldering, a Raspberry Pi Pico 2 W with its own Wi-Fi, and on ESP32-S3 boards. Every build and board, and where each stands: hardware/README.md.

For developers and contributors

Mono may become a dev board kit. We may open it to a first few developers and contributors before anything wider, and a sign-up sheet will come later. Until then, watch the repository or follow @picoquorum. Nothing is for sale, and no date is set.

Nothing signs unseen

The three-button screens, as the firmware draws them today at 240 × 135, the size of Mono's screen. The rail on the left names what each button does on that page. These were drawn for a board with its buttons down the left edge; Mono's own layout, with the buttons under the screen, is still to come.

The first of six pages of a review: transaction 0 on Base Sepolia, a transfer, Send 0.05 ETH. The rail offers Reject, Next and See 5.
Plain language. What it does and on which chain, one fact to a page.
A red page, 4 of 7: swap owner. The new owner, 0x90f7…b906, is not in the address book. Its address in full, with its blockie.
Red pages. Anything that changes who controls the Safe, or that it can't decode, is red all over, and Sign takes a longer hold.
Page 5 of 6: check with the proposer. The hash ends in 3120 5f57, with its blockie.
A verify code. The hash's last eight characters and its picture, to check with whoever proposed it.
Keep holding: 0.8 s to go. The Sign button fills with green, and the whole hash is on the screen.
Hold to sign. Every page seen first, then two seconds on Sign. Reject is one press, on any page.

How an approval goes

  1. 1

    Someone proposes

    In Safe{Wallet} or anywhere else. The transaction waits in Safe's queue for the owners.

  2. 2

    The console reads it

    It decodes the call into plain language, with red pages for anything that changes who controls the Safe, and computes the Safe transaction hash from the fields it shows.

  3. 3

    You hold Sign

    The key, a secure element on the console's board or plugged in over USB-C, signs the hash the console computed. It owns the Safe through Safe's audited passkey signer. No seed phrase exists.

  4. 4

    Execute in the app

    Every confirmation is checked in your browser, the signatures are laid out the way the Safe expects, and your wallet sends it.

Learn

Why a multisig, and why this device

One seed phrase is one point of failure. A multisig takes it away: several owners, and nothing moves until enough of them approve. Nine short explainers say why, how the hardware works and how it fails, and what holding a key asks of you. They are written and not yet recorded, so each script is there to read.

  • Start here. Why a multisig, what one is, and one approval from start to finish.
  • The hardware. The board, zone by zone, and every way it can fail.
  • Being an owner. Getting a key, a key with no backup, and what it protects and what it doesn't.
Open Learn

One owner, never the whole wallet

A Picoquorum is one vote in your Safe. It is built to sit next to the others: a hardware wallet, a passkey, Safe{Wallet} in a browser, another Picoquorum in another house.

No technology, and no person, should hold a threshold's worth of keys. Always keep owners on the Safe that are not this device.

What a sealed key can't protect you from

The app

Safe{Wallet} can't execute a transaction when a Picoquorum key is one of two or more confirmations: it fails with GS021. The Picoquorum app can, and checks everything on the way.

  • Safes. Owners, threshold and nonce read from the Safe itself. Save the ones you use, name the owners, back it all up to a file.
  • Propose. Sends, tokens, owner changes, thresholds and rejections, signed by your wallet as one owner, with the verify code the console will show.
  • Queue. Each transaction's hash recomputed, the console's verify code shown, every confirmation checked, and yours added from your wallet.
  • Execute. Simulated against the chain first, then sent by your browser wallet.
  • Keys. Each listed key's attestation checked in your browser, and a badge for the owners that pass.
  • Blockies everywhere. The same picture for an address or a hash as the console, Safe{Wallet} and Etherscan draw.
Launch app

Where it stands

  • A simulated Safe and a local fork, on the real Pico
  • Base Sepolia, end to end over HTTPS
  • Base mainnet: a chip's approval executed onchain, 2026-09-26
  • Next: Ethereum mainnet, with a fresh Trust M as one owner of a 3-of-5

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

The test ladder · Mainnet notes · Security model · Brand