Coconut Open Source Software Projects

“To help even one more person encounter Bitcoin the right way.”

Self-custody you can verify.

Coconut builds open Bitcoin self-custody tools that families can use with confidence today and pass on for generations.

01

Our philosophy

Simple enough for every family. Durable enough for generations.

Coconut began with a personal question: could we confidently recommend Bitcoin self-custody to our own parents and children? Our answer is to help people navigate Bitcoin's complexity with understanding—not hide it behind another trusted intermediary.

01

Confidence through understanding

People should not need to become experts, but they should be helped to understand the choices they make as they use Bitcoin.

02

Open standards over lock-in

PSBTs, descriptors, QR communication, and hardware wallet interoperability preserve choice across tools.

03

Designed for the long term

Self-custody should support not only secure use today, but recovery, continuity, and an eventual handoff to the next generation.

02

The projects

Open tools for verifiable self-custody.

Coconut develops its projects with Dart and Flutter to support Bitcoin wallet development optimized for mobile devices.

01Bitcoin library

coconut_lib

A Dart library for building mobile, air-gapped Bitcoin wallets and signers.

DartMIT
View repository
02Watch-only wallet

coconut_wallet

A watch-only Bitcoin wallet that syncs balances, creates transactions, and broadcasts signed transactions.

FlutterMIT/X11
View repository
03Offline signer

coconut_vault

An offline Bitcoin signer for managing keys and signing transactions on a network-disconnected device.

FlutterMIT/X11
View repository
04UI components

coconut_design_system

A reusable Flutter UI component library for building consistent Coconut application experiences.

FlutterMIT
View repository

03

How it fits together

Designed for stronger security and better usability.

Coconut separates each responsibility with purpose. coconut_lib is isolated to strengthen security, while coconut_design_system is separated to improve usability. coconut_wallet and coconut_vault remain distinct to preserve a strict air-gapped model: Wallet handles online coordination, while keys and signing stay offline in Vault.

04

Proof of work

Public work, verifiable at the source.

Coconut has been developed in public since March 2024, beginning in the pow_wallet repositories before moving to the current Coconut repositories. This dated snapshot links directly to the commit histories, releases, and source records behind the project.

4Public repositories
6,340Public commits
42GitHub releases
2024.03Developed in public since
RepositoryCommitsReleasesPublic sinceSource
coconut_lib363182024-09-13Inspect
coconut_wallet3,515192024-09-06Inspect
coconut_vault2,15552024-09-06Inspect
coconut_design_system307—2025-02-03Inspect

Last verified: August 10, 2026. Commit and release totals show the extent of public activity, not a ranking of quality or impact.

Review source evidence

05

Contributors

Built by people who chose to work in the open.

A diverse group of contributors has made many contributions across Coconut's repositories.

06

Licenses & permissions

Open code, clearly stated rights.

Subject to each project's license terms, you may use, copy, modify, distribute, sublicense, and commercially use the code. Copyright and permission notices must be retained.

  • 01Use
  • 02Copy
  • 03Modify
  • 04Distribute
  • 05Sublicense
  • 06Sell

07 / Contribute

Inspect it. Question it. Improve it with us.

Read the code, open an issue for something you find, or propose an improvement. Review each repository's contribution guide and responsible disclosure policy before contributing.