Project
Licensing
StateSync-GKR is distributed under the Business Source License 1.1. Learn what is free, what the verification-only production grant covers and when you need a commercial license.
This page explains the license of the current official StateSync-GKR distribution and helps you decide whether your use needs a commercial license.
Summary#
| Question | Answer |
|---|---|
| License | Business Source License 1.1, SPDX identifier BUSL-1.1 |
| Licensor | Oraclizer Labs, Inc. |
| Non-production use | Free, including research, development, testing, evaluation, auditing and benchmarking |
| Production use to verify proofs | Free under the Additional Use Grant, including embedding or distributing the verification functionality for that purpose |
| Production proving | Production use that generates proofs, embeds or redistributes the proving functionality in a product or service, or offers proof generation to third parties requires a commercial license |
| Change License | Apache License 2.0, three years after each version is first publicly distributed under the Business Source License |
The Business Source License is a source-available license. Before a version's Change Date, it is not an Open Source license.
License parameters#
| Parameter | Value |
|---|---|
| Licensed Work | StateSync-GKR, as defined in the LICENSE file of the distribution you received |
| Additional Use Grant | You may make production use of the Licensed Work solely to verify proofs, including embedding or distributing its verification functionality for that purpose. The grant does not extend to production use that generates proofs, that embeds or redistributes the proving functionality in a product or service, or that offers proof generation to third parties. Such use requires a commercial license from the Licensor. |
| Change Date | For each version, three years from the date that version is first publicly distributed under the Business Source License |
| Change License | Apache License, Version 2.0 |
On a version's Change Date, the Licensor grants you rights to that version under the Apache License 2.0, and the Business Source License grant for that version ends. Each version has its own Change Date.
What the license lets you do#
Without a commercial license, you may:
- copy, modify, create derivative works of and redistribute StateSync-GKR;
- make non-production use of it;
- make production use of it solely to verify proofs, as described by the Additional Use Grant.
The License also sets these conditions:
- You must conspicuously display the License on each original or modified copy.
- All copies of the original and modified work, and all derivative works, are subject to the License.
- If your use does not comply with the License, you must purchase a commercial license or stop using the Licensed Work.
- Use in violation of the License automatically ends your rights for the current version and all other versions.
- The License grants no right in the Licensor's trademarks or logos.
- The Licensed Work is provided as is, without warranties or conditions of any kind.
When you need a commercial license#
You need a commercial license from Oraclizer Labs, Inc. for production use that:
- generates proofs;
- embeds or redistributes the proving functionality of StateSync-GKR in a product or service;
- offers proof generation to third parties.
To discuss a commercial license, contact us through StateSync-GKR licensing.
Decide which license covers your use#
| Your situation | What covers it |
|---|---|
| Researching, evaluating, auditing or benchmarking StateSync-GKR | Business Source License 1.1, as non-production use |
| Developing and testing an integration in a non-production environment | Business Source License 1.1, as non-production use |
| Verifying proofs in a production system without generating them | Additional Use Grant |
| Embedding or distributing StateSync-GKR verification functionality in a product, solely to verify proofs | Additional Use Grant |
| Generating proofs in production | Commercial license |
| Including proving functionality in a product or service that you ship or operate | Commercial license |
| Offering proof generation to customers or other third parties | Commercial license |
| Using a version after its Change Date | Apache License 2.0 for that version |
If your case is not listed, or the line between verifying and proving is unclear in your design, contact us before production use. For general questions about the Business Source License, see the MariaDB BSL FAQ (opens in a new tab).
Earlier distributions#
Copies previously distributed lawfully under the MIT License or the Apache License 2.0 retain those permissions.
Contributions#
When you submit a contribution, you represent that you have the right to submit it and that it includes no third-party confidential or restricted material. You license the contribution under the Business Source License 1.1 that governs the repository.
You also grant Oraclizer Labs, Inc. a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license to reproduce, modify, distribute and sublicense your contribution under the Change License named in LICENSE, under commercial license terms offered by Oraclizer Labs, Inc., and under any later license of the repository. This grant lets each version convert to the Change License on its Change Date and lets commercial licenses cover the whole repository. If you cannot make this grant, for example because your employer holds the rights, say so in the pull request before the change is reviewed.
See CONTRIBUTING.md (opens in a new tab) for the full contribution terms. NOTICE (opens in a new tab) records the license history and the contributions accepted under earlier terms.
Other material#
- Third-party dependencies are licensed by their authors under their own terms.
- The data and figure files of the measurement dataset (dataset identifier to follow) are not licensed by the Business Source License. Their publication terms are decided separately and are still pending.