+×+
Open Source

Licenses & Attributions

Protocol 01 is built on the shoulders of exceptional open-source projects. We are grateful to the communities that make this possible.

Protocol 01 License

Protocol 01 — Core Protocol & Applications

BSL-1.1
View Source

The wallet application, browser extension, smart contracts, ZK circuits, and SDK packages are licensed under the Business Source License 1.1. Source code is viewable and forkable for non-commercial purposes. Commercial use requires explicit written permission.

Business Source License 1.1 — Copyright (c) 2024-2026 Protocol 01 Team. All rights reserved.

Licensed under the Business Source License 1.1 (the "License"); you may not use this software except in compliance with the License. You may obtain a copy of the License at mariadb.com/bsl11.

Additional Use Grant: You may use the Licensed Work for non-commercial and evaluation purposes. Production commercial use requires a separate commercial license from the Protocol 01 team.

Change Date: Four years from each release date.
Change License: Apache License, Version 2.0.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY.

Third-Party Dependencies

The following open-source packages are used in Protocol 01. We thank their maintainers and contributors.

Blockchain & Cryptography

PackageLicense
@solana/web3.jsMIT
@solana/spl-tokenApache-2.0
Anchor FrameworkApache-2.0
circom / snarkjsGPL-3.0
ark-circomMIT / Apache-2.0
ark-groth16MIT / Apache-2.0
poseidon-liteMIT
tweetnaclUnlicense

Authentication & Wallet

PackageLicense
@privy-io/expoMIT
@scure/bip39MIT
bs58MIT

State Management & Networking

PackageLicense
zustandMIT
axios (via fetch)MIT

Web & Build Tools

PackageLicense
Next.jsMIT
Tailwind CSSMIT
TypeScriptApache-2.0
ViteMIT

Rust Backend (Prover Service)

PackageLicense
axumMIT
tokioMIT
ark-bn254MIT / Apache-2.0
wasmerMIT

Notice

This list represents the major dependencies used in Protocol 01 and is not exhaustive. Each package may have its own transitive dependencies with their own licenses. The full license text for each dependency can be found in the respective package's repository. If you believe an attribution is missing or incorrect, please contact us at legal@protocol-01.com.