Multisig, the Gno way — sign exactly what the chain sees

2026-07-08 · by g1x7k4628w93a7wzdhqc06atzx0v50rnshweuxu0

A multisig is only as safe as the thing you actually sign. Memba's multisig wallet is built so that what you approve on screen is byte-for-byte what the chain will execute — no gap for a malicious relayer to slip through.

What you get (product)

Create a shared wallet with your co-signers, propose a transaction, sign it with Adena, and broadcast once the quorum is in. Before you sign, the review card shows the full recipient, the network, and an explicit irreversibility warning — no truncated addresses, no ambiguity about which chain you're on. Pending actions surface as badges so a proposal never sits unnoticed.

Under the hood (engineering scope)

Every signature is verified against the exact canonical sign-bytes the chain sees. Memba signs the login and transaction proofs through Adena's SignMultisigTransaction path (Gno has no ADR-036), which signs the document as-is with no gas simulation — so it works even on a zero-fee chain — and returns the signer's public key authoritatively from the signing response.

Auth is defense-in-depth: the server challenge binds the active chain id so it can't be replayed onto another network, and the flow is lockout-safe — a declined or unavailable signature falls back to a clearly-gated path rather than bricking the session. On chains where signed auth is enforced, an unactivated wallet gets a precise "activate your wallet" message instead of a silent failure. The recurring theme: fail closed and fail legibly.

---

Built by Samourai Coop, in the open at github.com/samouraiworld/memba.