Why open source matters for crypto
A cryptocurrency wallet manages the most sensitive data you can hold on a device: the private keys that control your funds. When that wallet is closed source, you are placing absolute trust in the developer. You cannot verify what the code does with your keys, whether it phones home, or whether a backdoor exists.
The history of cryptocurrency is littered with closed-source wallets that were later discovered to contain vulnerabilities, telemetry, or outright theft mechanisms. Open source eliminates this category of risk by making the code available for review by anyone — security researchers, independent auditors, and the community at large.
Open source does not guarantee security on its own, but it is a necessary precondition for verifiable security. Combined with reproducible builds and independent audits, it forms a complete chain of trust that does not depend on believing the developer.
MIT license
Jaxx Liberty is released under the MIT license, one of the most permissive open-source licenses available. The MIT license grants you the freedom to use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software without restriction, provided that the copyright notice and license text are included in all copies.
This means you can fork the project, build your own version, integrate it into other products, or use it as a reference implementation for your own wallet — all without asking permission. The MIT license was chosen because it aligns with the ethos of cryptocurrency: open, permissionless, and free.
What you can inspect
Key generation
The entropy source, BIP-39 mnemonic derivation, and BIP-44 key hierarchy. Verify that keys are generated securely and deterministically.
Transaction signing
The full signing pipeline for every supported blockchain. Confirm that transactions are constructed and signed correctly.
Network communication
Every API call, every endpoint, every byte sent over the wire. Verify that the wallet talks only to blockchain networks and nothing else.
Local storage
How keys are encrypted and stored on your device. Confirm that no sensitive data is written to unprotected storage or transmitted externally.
Contributing
Jaxx Liberty welcomes contributions from the community. Whether you are a security researcher, a developer, a designer, or a translator, there are ways to get involved. Fork the repository, make your changes, and submit a pull request for review.
All contributions go through a code review process before being merged. Security-critical changes require additional review by the core team. The project follows standard open-source best practices: clear commit messages, comprehensive tests, and documentation for new features.
Reproducible builds
Open source means you can read the code. Reproducible builds mean you can verify that the code you read is the code that runs. Jaxx Liberty's build process is deterministic: given the same source code and build environment, anyone can produce a binary that is bit-for-bit identical to the official release.
This closes the gap between "the source looks safe" and "the binary I downloaded is safe." It eliminates the need to trust the build pipeline, the CI server, or the release manager.
Security through transparency
Transparency is not a marketing feature — it is a security mechanism. Every component of Jaxx Liberty's security model is designed to be independently verifiable. The code is open for review. The builds are reproducible. The audits are published. The architecture is documented.
When a wallet asks for trust, ask what it offers in return. Jaxx Liberty offers proof.
Read the code
Jaxx Liberty is open source under the MIT license. Inspect it, build it, verify it.
Open Wallet