BUSL

Nami makes the source code of its smart contracts publicly available to support inspection, testing, and independent review.

Access to the source code does not grant permission to deploy it, operate it in production, or use derivative works in production.

Most of the protocol's proprietary smart contracts are published under the Business Source License 1.1 (BUSL-1.1).

Any fork, derivative deployment, or production use of code subject to the BUSL requires prior written authorization from the Licensor.

Interfaces and libraries intended for interaction with Nami's official deployments are published under the MIT License.

Components derived from external projects remain subject to their applicable licenses.

This page provides a general overview.

The LICENSE file distributed with each repository or release, together with the SPDX identifier included in each source file, defines the terms applicable to that code.

License Structure

Nami Proprietary Code

Code subject to the BUSL-1.1 may be inspected and used for local development, testing, simulation, research, and security review in accordance with the terms of the license.

Without prior written authorization, code subject to the BUSL may not be:

• Distributed or used in a production environment;
• Used to operate an active live protocol, application, or service;
• Incorporated into an operational product or service;
• Used to deploy modified or derivative versions of the contracts;
• Commercialized directly or through a third-party product or service.

These restrictions also apply to modified copies and derivative works based on the protected code.

Integrating with Nami

Interacting with Nami's official deployments does not require deploying code subject to the BUSL.

Frontends, wallets, routers, aggregators, vaults, analytics platforms, automation services, and other applications may use the MIT-licensed interfaces and libraries to access the Nami's public functions.

Any integration that incorporates, modifies, or distributes Nami's proprietary code remains subject to the applicable license and may require commercial authorization.

Transparency and Security Research

Publishing the source code allows developers, researchers, and users to verify how Nami's smart contracts operate.

The code may be examined through manual review, local testing, simulation, and automated analysis tools. Copies used for these purposes must retain the required license text and copyright notices.

Vulnerabilities affecting active deployments must be reported without delay through one of Nami's official channels: a support ticket in the official Discord server, a direct message to Nami's official account on X, or email at [email protected].

Third-Party Components

Nami incorporates and interacts with software developed by third parties. These components remain subject to their respective licenses, notices, and commercial agreements.

Algebra Integral is licensed by Algebra and deployed by Nami under a separate agreement. Publication of the Nami codebase does not grant any additional rights to Algebra's proprietary code.

The Nami Marketplace uses the canonical Seaport 1.6 deployment for settlement. Seaport is governed by its own MIT License.

Additional dependencies, including those provided by OpenZeppelin, Chainlink, Solady, and Foundry, remain subject to their respective licenses and attribution requirements.

Commercial Authorization

Projects intending to deploy, use, or incorporate Nami code subject to the BUSL in production must obtain prior written authorization.

Requests may be submitted to [email protected] and should describe the project, the components involved, and the intended use.

Submitting a request does not grant any rights to the code.

Any authorization granted for commercial use must be formalized through a written agreement with the Licensor.

Applicable Terms

Terms may vary between files and components. The applicable terms are determined by:

1. The SPDX identifier included in the relevant source file;
2. The LICENSE file distributed with the relevant repository or release;
3. Any license or notice included with a third-party dependency;
4. Any separate written agreement issued by the applicable Licensor.

The parameters governing each release subject to the BUSL are defined in its corresponding LICENSE file.

If this page differs from the license distributed with the relevant code, the terms of that license prevail.