Overview
Round Table is an open-source multisig wallet for Cardano, built by the ADAO Community as a browser-based tool for creating and co-signing shared native-script wallets1. It is aimed at DAOs, project treasuries, and small groups that need multiple approvals before funds can move. The application runs entirely client-side, with no backend server holding user data or keys, so signing happens locally in the participant's connected wallet2.
Key Features
- Client-side architecture. The app runs in the browser with no backing server, keeping wallet state and signing flows on the user's device rather than on shared infrastructure2.
- Native script multisig. Shared wallets are defined as Cardano native scripts, enforcing M-of-N signing rules at the protocol level rather than through off-chain coordination1.
- Multi-wallet connector support. Co-signers can plug in using Nami, Eternl, Gero, Flint, or Typhon, so each participant keeps their preferred signing tool2.
- Open-source codebase. The TypeScript source is published under the ADAOcommunity GitHub organization under an Apache 2.0 license, allowing independent review, self-hosting, and forks3.
- DAO-oriented design. Round Table was produced by a Cardano DAO community and is framed around shared treasuries and group decision-making, with flows focused on creating wallets, proposing transactions, and gathering signatures1.
What to Expect
Using Round Table starts by visiting the hosted app and creating either a personal wallet or a new multisig configuration, choosing how many signers are required out of the total set of participants. The interface is minimal and functional rather than heavily designed, in line with a community-built tool focused on utility over polish. Because everything runs client-side, there are no accounts to register and no server-side history to rely on, so participants are expected to share wallet configurations and pending transactions between themselves through their own channels.
Day-to-day use involves connecting a Cardano browser wallet, reviewing a proposed transaction, and signing it with the connected extension. Once the required threshold of signatures is collected, the transaction can be submitted to the network through the connected wallet. The client-side model means users retain full custody throughout, but it also places more responsibility on participants to back up wallet metadata and coordinate signing rounds themselves, since nothing is stored remotely on their behalf.
Users evaluating Round Table should weigh its clean client-side architecture and open-source codebase against the state of ongoing maintenance on the public repository before adopting it for high-value treasuries3. For groups that need a lightweight, self-custodial way to manage a shared Cardano wallet, it remains a usable reference implementation, and newcomers may want to compare it against other options listed in the multisig wallets category on Adastack.
