Bitcoin MultiSig for All
Bitcoin has been designed to provide financial freedom, exclude middlemen and to allow everyone to trade openly, safeguarding privacy and security. This project aims to bring MultiSig to the masses, explain technical jargon through metaphors to a 5yo, deliver simple tools and exercises to easily learn more and feel confident practicing Self-Custody and achieve financial sovereignty.
The journey of onboarding a user and create a multiSig setup begins far before buying a hardware wallet or installing a wallet app.
Bitcoin Safe seems designed for families and people that want to start exploring and learning about multiSig setup. The need for such application of bitcoin could go much further defining best practices for private organizations that aim to custody bitcoin in a private and anonymous way, following and enjoy the values and standards bitcoin has been built for.
Organizations and small private groups like families, family offices and solopreneurs operating on a bitcoin standard will have the need to keep track of transactions and categorize them to keep the books in order. A part of our efforts will be spent ensuring accessibility standards are in place for everyone to use Bitcoin Safe with comfort and safety.
We aim with this project to bring together the three ideas below:
Bitcoin Safe
Looking for design improvements and ideas (not a complete redesign of the entire app) Bitcoin Safe.
The program can be downloaded and tested (with testnet) on: https://bitcoin-safe.org
Particularly looking for design ideas for:
- Onboarding (Bitcoin Safe includes a wallet setup wizard)
- Category component in the address tab (can rename, drag to address, delete, add categories. Addresses can be dropped on categories)
- Category selection in the send tab (how to select a category to choose the coins from)
No User Left Behind
Let’s build accessible Bitcoin tools—together.
We’ll (we as in the team we gather) kick things off with a hands-on accessibility workshop where we sit down, explore real Bitcoin apps, and collaborate to make them easier to use—especially for people with disabilities, but ultimately for everyone.
As we test and improve these tools, we’ll take notes, share insights, and collect best practices. The goal? To turn our learnings into a living, open-source resource: an Accessibility Guide for Bitcoin devs and designers.
This guide will be practical, easy to follow, and filled with real examples from the Bitcoin ecosystem—something anyone can use to design more inclusive and user-friendly apps from the start.
It’s about learning, doing, and documenting—together. example: https://bitcoin.design/guide/designing-products/accessibility/
Why Accessibility Matters
Accessibility ensures that everyone—regardless of physical ability, vision, hearing, cognitive challenges, or tech literacy—can use and benefit from the tools we build. In the Bitcoin and open-source world, we talk a lot about freedom, inclusion, and decentralization. But if our apps aren’t usable by people with disabilities, we’re unintentionally leaving a huge part of the global population behind.
Improving accessibility isn’t just the right thing to do—it also makes apps better for everyone. Thoughtful design leads to cleaner interfaces, better navigation, and more reliable interactions across all types of users.
By working on accessibility, we’re not just fixing bugs or adding features—we’re expanding the reach of Bitcoin and digital freedom to truly include everyone.
At last we can also make a website (Start with Accessibility) with helpful videos.
Self-custody guidelines for organizations
This has been brought up in the Bitcoin Design Discord. As more organization (governments, companies, non-profits…) adopt bitcoin for their treasuries, many of them ideally do so in a self-custodial way. This is quite intricate and right now everyone has to come up with their own solution. Can we come up with best practices and guidelines to make that easier?
Here is an idea for a project for anyone(s) motivated by it. I’m not aware of any published guidelines for entities ranging from governments to companies to non-profit entities to handle self custody procedures. How many people should hold keys, who should hold them, how should they hold them, and how should key transfer happen when people leave or there is a transition of power? For example, let’s say a country like El Salvador has a bitcoin reserve, and instead of relying on a US-based company to custody their bitcoin (which is much like a country storing their gold in NYC), instead they want to be self-sovereign and custody themselves. Not only do they care about being safe and secure, but they also need to answer the questions above, who holds the keys. And when a new person is elected president, how does that key transfer occur, handling both peaceful and non-peaceful transfer of power? Or, even a simpler case, such as a small non-profit like Bitcoin Development Kit Foundation or ₿trust, how should they handle this? Right now, I believe every organization has to roll their own solution. This is intimidating and a barrier to doing self custody. I suspect many opt for custodial due to this. And for those that self custody, most probably have an inferior solution than if they adopted a well-thought-out Bitcoin Design Guide guidelines.
— @moneyball