From b40442a1776f57b719d29c64102743ca2d3424ff Mon Sep 17 00:00:00 2001
From: Cameron Marshall
Date: Fri, 13 Mar 2026 11:35:30 -0400
Subject: [PATCH] rebase
---
.../provable-sdk-tutorial-docs/SKILL.md | 177 +-
.claude/CLAUDE.md | 99 +-
.claude/commands/wrap-snarkvm.md | 57 +-
.codecov.yml | 8 +-
.github/ISSUE_TEMPLATE.md | 3 +-
.github/ISSUE_TEMPLATE/config.yml | 8 +-
.github/ISSUE_TEMPLATE/documentation.md | 2 +-
.github/ISSUE_TEMPLATE/feature.md | 7 +-
.github/ISSUE_TEMPLATE/proposal.md | 2 +-
.github/actions/setup-rust/action.yml | 26 +-
.github/actions/setup-yarn/action.yml | 18 +-
.github/actions/use-build/action.yml | 12 +-
.github/dependabot.yml | 108 +-
.github/workflows/sdk.yml | 479 ++--
.github/workflows/staging-website.yml | 62 +-
.github/workflows/update-snarkvm.yml | 286 +-
.github/workflows/website.yml | 62 +-
.prettierignore | 1 +
LICENSE.md | 869 ++++---
PUBLISH.md | 2 +-
README.md | 73 +-
create-leo-app/README.md | 11 +-
create-leo-app/build.config.ts | 24 +-
create-leo-app/index.js | 2 +-
create-leo-app/package.json | 84 +-
create-leo-app/src/index.ts | 547 ++--
.../package.json | 34 +-
.../rollup.config.js | 2 +-
.../src/index.ts | 21 +-
.../tsconfig.json | 24 +-
create-leo-app/template-devnode-js/README.md | 34 +-
create-leo-app/template-devnode-js/index.js | 53 +-
.../template-devnode-js/package.json | 20 +-
create-leo-app/template-extension/README.md | 3 +-
.../template-extension/package.json | 26 +-
.../template-extension/src/service_worker.js | 5 +-
.../template-extension/src/worker.js | 16 +-
.../template-extension/static/manifest.json | 26 +-
.../template-extension/static/offscreen.html | 14 +-
create-leo-app/template-nextjs-ts/README.md | 2 +-
.../template-nextjs-ts/next.config.js | 34 +-
.../template-nextjs-ts/package.json | 44 +-
.../template-nextjs-ts/src/app/globals.css | 183 +-
.../template-nextjs-ts/src/app/layout.tsx | 28 +-
.../src/app/page.module.css | 228 +-
.../template-nextjs-ts/src/app/page.tsx | 2 +-
.../template-nextjs-ts/src/app/worker.ts | 66 +-
.../template-nextjs-ts/tsconfig.json | 50 +-
.../README.md | 4 +-
.../src/index.ts | 56 +-
.../README.md | 21 +-
.../loyalty_rewards/build/abi.json | 536 ++--
.../build/imports/loyalty_token.abi.json | 842 +++---
.../loyalty_rewards/build/program.json | 14 +-
.../loyalty_rewards/program.json | 26 +-
.../loyalty_token/build/abi.json | 842 +++---
.../loyalty_token/build/program.json | 14 +-
.../src/index.ts | 577 ++--
create-leo-app/template-node-ts/package.json | 34 +-
.../template-node-ts/rollup.config.js | 2 +-
create-leo-app/template-node-ts/src/index.ts | 99 +-
create-leo-app/template-node-ts/tsconfig.json | 24 +-
create-leo-app/template-node/index.js | 73 +-
create-leo-app/template-node/package.json | 20 +-
.../README.md | 53 +-
.../package.json | 34 +-
.../rollup.config.js | 2 +-
.../src/helpers.ts | 40 +-
.../src/index.ts | 155 +-
.../tsconfig.json | 24 +-
.../template-private-transaction-ts/README.md | 5 +-
.../package.json | 34 +-
.../rollup.config.js | 2 +-
.../src/index.ts | 23 +-
.../tsconfig.json | 24 +-
.../README.md | 9 +-
.../src/App.tsx | 20 +-
.../src/workers/worker.ts | 57 +-
.../template-react-leo/.eslintrc.cjs | 36 +-
create-leo-app/template-react-leo/README.md | 52 +-
.../template-react-leo/helloworld/README.md | 2 +
create-leo-app/template-react-leo/index.html | 156 +-
.../template-react-leo/package.json | 84 +-
create-leo-app/template-react-leo/src/App.css | 42 +-
create-leo-app/template-react-leo/src/App.jsx | 172 +-
.../template-react-leo/src/index.css | 86 +-
.../template-react-leo/src/main.jsx | 6 +-
.../src/workers/AleoWorker.js | 4 +-
.../template-react-leo/src/workers/worker.js | 92 +-
.../template-react-leo/vite.config.js | 20 +-
.../template-react-leo/webpack.config.js | 175 +-
.../README.md | 31 +-
.../index.html | 20 +-
.../loyalty_rewards/build/abi.json | 536 ++--
.../build/imports/loyalty_token.abi.json | 842 +++---
.../loyalty_rewards/build/program.json | 14 +-
.../loyalty_rewards/program.json | 28 +-
.../loyalty_token/build/abi.json | 842 +++---
.../loyalty_token/build/program.json | 14 +-
.../package.json | 96 +-
.../src/App.css | 499 ++--
.../src/App.tsx | 1025 ++++----
.../src/index.css | 38 +-
.../src/main.tsx | 6 +-
.../src/vite-env.d.ts | 28 +-
.../src/workers/AleoWorker.ts | 54 +-
.../src/workers/worker.ts | 2309 +++++++++--------
.../tsconfig.json | 30 +-
.../vite.config.ts | 20 +-
.../webpack.config.ts | 178 +-
.../.eslintrc.cjs | 36 +-
.../template-react-managed-worker/README.md | 3 +-
.../template-react-managed-worker/index.html | 156 +-
.../package.json | 78 +-
.../template-react-managed-worker/src/App.css | 42 +-
.../template-react-managed-worker/src/App.jsx | 129 +-
.../src/index.css | 86 +-
.../src/main.jsx | 6 +-
.../vite.config.js | 26 +-
.../webpack.config.js | 146 +-
.../template-react-ts/.eslintrc.cjs | 36 +-
create-leo-app/template-react-ts/README.md | 52 +-
.../template-react-ts/helloworld/README.md | 2 +
create-leo-app/template-react-ts/index.html | 156 +-
create-leo-app/template-react-ts/package.json | 94 +-
create-leo-app/template-react-ts/src/App.css | 42 +-
create-leo-app/template-react-ts/src/App.tsx | 172 +-
.../template-react-ts/src/custom.d.ts | 18 +-
.../template-react-ts/src/index.css | 86 +-
create-leo-app/template-react-ts/src/main.tsx | 6 +-
.../src/workers/AleoWorker.ts | 4 +-
.../template-react-ts/src/workers/worker.ts | 92 +-
.../template-react-ts/tsconfig.json | 28 +-
.../template-react-ts/vite.config.ts | 20 +-
.../template-react-ts/webpack.config.ts | 192 +-
create-leo-app/template-vanilla/main.js | 2 +-
.../template-vanilla/vite.config.js | 4 +-
create-leo-app/template-vanilla/worker.js | 85 +-
create-leo-app/tsconfig.json | 26 +-
docs/00_overview.md | 69 +-
docs/create-leo-app/01_intro.md | 64 +-
docs/create-leo-app/02_react_js_tutorial.md | 52 +-
docs/examples/01_transfer_public.md | 28 +-
docs/examples/02_transfer_private.md | 56 +-
docs/examples/03_deploy_program.md | 19 +-
docs/examples/04_execute_program.md | 19 +-
docs/guide/01_intro.md | 66 +-
docs/guide/02_setup.md | 60 +-
docs/guide/03_creating_accounts.md | 69 +-
docs/guide/04_programs.md | 131 +-
docs/guide/05_transfers.md | 194 +-
docs/guide/06_executing_programs.md | 194 +-
docs/guide/07_deploying_programs.md | 109 +-
docs/guide/08_public_program_state.md | 115 +-
docs/guide/09_private_program_state.md | 156 +-
docs/guide/10_finding_records.md | 147 +-
docs/guide/11_working_with_chain_state.md | 297 ++-
e2e/dynamic/index.js | 40 +-
e2e/dynamic/package.json | 20 +-
e2e/mainnet/index.js | 48 +-
e2e/mainnet/package.json | 20 +-
e2e/nodenext/index.ts | 8 +-
e2e/nodenext/tsconfig.json | 12 +-
e2e/testnet/index.js | 48 +-
e2e/testnet/package.json | 20 +-
package.json | 76 +-
scripts/change-version.js | 57 +-
sdk/.eslintrc.json | 28 +-
sdk/README.md | 22 +-
sdk/docs/index.html | 1332 +++++++++-
sdk/jsdoc.json | 67 +-
sdk/package.json | 162 +-
sdk/rollup.config.js | 56 +-
sdk/rollup.test.js | 11 +-
sdk/src/account.ts | 891 ++++---
sdk/src/browser.ts | 95 +-
sdk/src/constants.ts | 20 +-
sdk/src/integrations/sealance/merkle-tree.ts | 362 +--
sdk/src/keys/keystore/error.ts | 2 +-
sdk/src/keys/keystore/file.ts | 57 +-
sdk/src/keys/keystore/interface.ts | 10 +-
sdk/src/keys/provider/interface.ts | 2 +-
sdk/src/keys/provider/memory.ts | 20 +-
sdk/src/keys/provider/offline.ts | 354 ++-
sdk/src/keys/verifier/interface.ts | 7 +-
sdk/src/keys/verifier/memory.ts | 37 +-
sdk/src/models/authorization.ts | 2 +-
sdk/src/models/blockJSON.ts | 12 +-
sdk/src/models/confirmed_transaction.ts | 2 +-
sdk/src/models/cryptoBoxPubkey.ts | 6 +-
sdk/src/models/deployment/deploymentJSON.ts | 8 +-
sdk/src/models/deployment/deploymentObject.ts | 6 +-
sdk/src/models/encryptedProvingRequest.ts | 6 +-
sdk/src/models/finalizeJSON.ts | 8 +-
sdk/src/models/functionInput.ts | 12 +-
sdk/src/models/functionObject.ts | 10 +-
sdk/src/models/imports.ts | 2 +-
sdk/src/models/input/inputJSON.ts | 2 +-
sdk/src/models/input/inputObject.ts | 8 +-
sdk/src/models/inputID.ts | 2 +-
sdk/src/models/keyPair.ts | 2 +-
sdk/src/models/output/outputObject.ts | 14 +-
sdk/src/models/owner/ownerJSON.ts | 2 +-
sdk/src/models/plaintext/array.ts | 5 +-
sdk/src/models/plaintext/literal.ts | 2 +-
sdk/src/models/plaintext/plaintext.ts | 6 +-
sdk/src/models/plaintext/struct.ts | 2 +-
sdk/src/models/provingRequest.ts | 2 +-
sdk/src/models/provingResponse.ts | 12 +-
sdk/src/models/ratification.ts | 2 +-
.../models/record-provider/encryptedRecord.ts | 6 +-
sdk/src/models/record-provider/ownedRecord.ts | 2 +-
.../record-provider/recordSearchParams.ts | 4 +-
.../record-scanner/encryptedRecordsResult.ts | 5 +-
sdk/src/models/record-scanner/error.ts | 1 -
sdk/src/models/record-scanner/ownedFilter.ts | 6 +-
.../ownedRecordsResponseFilter.ts | 4 +-
.../record-scanner/ownedRecordsResult.ts | 1 -
.../models/record-scanner/recordsFilter.ts | 4 +-
.../record-scanner/recordsResponseFilter.ts | 4 +-
.../record-scanner/registrationRequest.ts | 4 +-
.../record-scanner/registrationResponse.ts | 8 +-
.../record-scanner/serialNumbersResult.ts | 1 -
.../models/record-scanner/statusResponse.ts | 4 +-
sdk/src/models/record-scanner/statusResult.ts | 1 -
sdk/src/models/record-scanner/tagsResult.ts | 1 -
sdk/src/models/request.ts | 4 +-
sdk/src/models/solution.ts | 2 +-
.../models/transaction/transactionObject.ts | 17 +-
sdk/src/models/transition/transitionJSON.ts | 4 +-
sdk/src/models/transition/transitionObject.ts | 4 +-
sdk/src/network-client.ts | 194 +-
sdk/src/polyfill/fetch.ts | 10 +-
sdk/src/polyfill/worker.ts | 32 +-
sdk/src/polyfill/xmlhttprequest.ts | 6 +-
sdk/src/program-manager.ts | 511 ++--
sdk/src/record-provider.ts | 148 +-
sdk/src/record-scanner.ts | 203 +-
sdk/src/security.ts | 26 +-
sdk/src/utils.ts | 29 +-
sdk/src/wasm.ts | 4 +-
sdk/tests/account.test.ts | 268 +-
sdk/tests/algorithm.test.ts | 268 +-
sdk/tests/arithmetic.test.ts | 130 +-
sdk/tests/data/account-data.ts | 105 +-
sdk/tests/data/algebra.ts | 158 +-
sdk/tests/data/program.ts | 27 +-
sdk/tests/data/proving.ts | 14 +-
sdk/tests/data/records.ts | 440 ++--
sdk/tests/key-provider.test.ts | 566 +++-
sdk/tests/network-client.integration.ts | 99 +-
sdk/tests/network-client.test.ts | 141 +-
sdk/tests/program-manager.test.ts | 403 ++-
sdk/tests/record-provider.integration.ts | 29 +-
sdk/tests/record-provider.test.ts | 22 +-
sdk/tests/record-scanner-integration.spec.ts | 22 +-
sdk/tests/record-scanner.test.ts | 322 ++-
sdk/tests/sealance-merkle-tree.test.ts | 334 +--
sdk/tests/wasm.test.ts | 531 ++--
sdk/tsconfig.json | 52 +-
sdk/tsconfig.test.json | 8 +-
wasm/LICENSE.md | 869 ++++---
wasm/README.md | 54 +-
wasm/build.js | 153 +-
wasm/package.json | 98 +-
wasm/test.js | 10 +-
website/.eslintrc.cjs | 2 +-
website/README.md | 12 +-
website/index.html | 53 +-
website/src/App.css | 12 +-
website/src/components/WasmLoadingMessage.jsx | 11 +-
website/src/index.jsx | 6 +-
website/src/main.jsx | 49 +-
website/src/pages/Homepage.css | 5 +-
website/src/pages/Homepage.jsx | 52 +-
website/src/pages/PrivacyPolicy.css | 11 +-
website/src/pages/PrivacyPolicy.jsx | 140 +-
website/src/pages/TermsOfUse.jsx | 402 +--
website/src/routing.jsx | 5 +-
.../tabs/account/AccountFromPrivateKey.jsx | 12 +-
.../src/tabs/account/AddressFromViewKey.jsx | 11 +-
website/src/tabs/account/NewAccount.jsx | 7 +-
website/src/tabs/account/SignMessage.jsx | 14 +-
website/src/tabs/account/VerifyMessage.jsx | 5 +-
website/src/tabs/advanced/DecryptAccount.jsx | 18 +-
website/src/tabs/advanced/EncryptAccount.jsx | 7 +-
website/src/tabs/algebra/FieldArithmetic.jsx | 91 +-
website/src/tabs/algebra/GroupArithmetic.jsx | 122 +-
website/src/tabs/algebra/HashFunctions.jsx | 443 +++-
website/src/tabs/develop/Deploy.jsx | 69 +-
website/src/tabs/develop/ExecuteLegacy.jsx | 8 +-
website/src/tabs/develop/Join.jsx | 24 +-
website/src/tabs/develop/Split.jsx | 12 +-
website/src/tabs/develop/Transfer.jsx | 8 +-
website/src/tabs/develop/execute/index.jsx | 455 ++--
website/src/tabs/protocol/DecryptRecord.css | 2 +-
website/src/tabs/protocol/DecryptRecord.jsx | 12 +-
website/src/tabs/protocol/TransactionInfo.jsx | 1237 +++++----
website/src/tabs/protocol/transactions.js | 6 +-
website/src/tabs/rest/GetBlockByHash.jsx | 9 +-
website/src/tabs/rest/GetBlockByHeight.jsx | 9 +-
website/src/tabs/rest/GetLatestBlock.jsx | 16 +-
.../src/tabs/rest/GetLatestBlockHeight.jsx | 20 +-
website/src/tabs/rest/GetMappingNames.jsx | 7 +-
website/src/tabs/rest/GetMappingValue.jsx | 12 +-
website/src/tabs/rest/GetProgram.jsx | 9 +-
website/src/tabs/rest/GetTransaction.jsx | 13 +-
website/src/workers/worker.js | 246 +-
website/vercel.json | 44 +-
website/vite.config.js | 2 +-
website/webpack.config.js | 22 +-
311 files changed, 19417 insertions(+), 13524 deletions(-)
create mode 100644 .prettierignore
diff --git a/.agents/skills/provable-sdk-tutorial-docs/SKILL.md b/.agents/skills/provable-sdk-tutorial-docs/SKILL.md
index 999f4940e..3d033e254 100644
--- a/.agents/skills/provable-sdk-tutorial-docs/SKILL.md
+++ b/.agents/skills/provable-sdk-tutorial-docs/SKILL.md
@@ -1,6 +1,9 @@
---
name: provable-sdk-tutorial-docs
-description: Use when writing tutorial documentation or create-leo-app examples for the Provable SDK (@provablehq/sdk). Covers how to structure runnable templates, write tutorial-style docs, and handle Node.js vs web runtime differences.
+description:
+ Use when writing tutorial documentation or create-leo-app examples for the
+ Provable SDK (@provablehq/sdk). Covers how to structure runnable templates,
+ write tutorial-style docs, and handle Node.js vs web runtime differences.
---
# Provable SDK Tutorial Docs
@@ -8,10 +11,12 @@ description: Use when writing tutorial documentation or create-leo-app examples
## Overview
This skill guides writing two interconnected artifacts for each SDK feature set:
+
1. A runnable **create-leo-app template** demonstrating the features
2. **Tutorial documentation** that walks readers through the template
-The template and tutorial are the same content expressed two ways — step numbers, section names, and code structure must correspond exactly.
+The template and tutorial are the same content expressed two ways — step
+numbers, section names, and code structure must correspond exactly.
---
@@ -19,39 +24,56 @@ The template and tutorial are the same content expressed two ways — step numbe
Require the developer to specify:
-| Input | Description |
-|-------|-------------|
-| **Feature bucket** | Explicit list of SDK features to demonstrate (e.g. "key caching, offline execution, deployment") |
-| **Target runtimes** | `node`, `web`, or `both` |
-| **Highlight areas** | What concepts readers should leave understanding — not just what the code does, but WHY |
-| **Complexity level** | beginner / intermediate / advanced — determines how much Aleo/ZK background to assume |
+| Input | Description |
+| -------------------- | ------------------------------------------------------------------------------------------------ |
+| **Feature bucket** | Explicit list of SDK features to demonstrate (e.g. "key caching, offline execution, deployment") |
+| **Target runtimes** | `node`, `web`, or `both` |
+| **Highlight areas** | What concepts readers should leave understanding — not just what the code does, but WHY |
+| **Complexity level** | beginner / intermediate / advanced — determines how much Aleo/ZK background to assume |
---
## SDK Runtime Context
-Tutorials must open with context about why someone would use the SDK in this environment. Use the framing below as a guide.
+Tutorials must open with context about why someone would use the SDK in this
+environment. Use the framing below as a guide.
### Node.js
The SDK runs natively in Node — no WASM worker setup needed. Common use cases:
-- **Backend servers** that execute web3 functions on behalf of users (e.g. building and submitting transactions server-side)
-- **Hardware wallets** that execute transactions in an offline setting on behalf of users
-- **Command-line tools** and scripts for account management, transaction creation, or record or chain data inspection, or specialized functions such as MPC computations run by web3 service providers
-- **Local testing and prototyping** local testing of dapps or web3 service prototypes
+- **Backend servers** that execute web3 functions on behalf of users (e.g.
+ building and submitting transactions server-side)
+- **Hardware wallets** that execute transactions in an offline setting on behalf
+ of users
+- **Command-line tools** and scripts for account management, transaction
+ creation, or record or chain data inspection, or specialized functions such as
+ MPC computations run by web3 service providers
+- **Local testing and prototyping** local testing of dapps or web3 service
+ prototypes
### Web (Browser)
-In browser contexts, the SDK is most commonly used to **supplement features that wallet adapters don't yet provide**. The [aleo-wallet-adapter](https://github.com/ProvableHQ/aleo-dev-toolkit/tree/master/packages/aleo-wallet-adaptor) handles account management and basic transaction signing — developers reach for the SDK directly when they need:
+In browser contexts, the SDK is most commonly used to **supplement features that
+wallet adapters don't yet provide**. The
+[aleo-wallet-adapter](https://github.com/ProvableHQ/aleo-dev-toolkit/tree/master/packages/aleo-wallet-adaptor)
+handles account management and basic transaction signing — developers reach for
+the SDK directly when they need:
-- Cryptographic hashing (BHP, Pedersen, Poseidon) and mathematics (cryptographic math using the Aleo finite field and groups)
-- Program and program data introspection (parsing program source, inspecting program functions, records and mappings)
-- Arbitrary encryption, decryption and signature operations not exposed by the wallet.
+- Cryptographic hashing (BHP, Pedersen, Poseidon) and mathematics (cryptographic
+ math using the Aleo finite field and groups)
+- Program and program data introspection (parsing program source, inspecting
+ program functions, records and mappings)
+- Arbitrary encryption, decryption and signature operations not exposed by the
+ wallet.
-**Web tutorials must recommend using `aleo-wallet-adapter` alongside the SDK** for account/signing concerns, transaction execution and should show how the two integrate where relevant. Do not suggest the SDK replaces the wallet adapter on the web.
+**Web tutorials must recommend using `aleo-wallet-adapter` alongside the SDK**
+for account/signing concerns, transaction execution and should show how the two
+integrate where relevant. Do not suggest the SDK replaces the wallet adapter on
+the web.
-WASM runs in a Web Worker in browsers, this is optional but highly recommend. Every web template should at least suggestion the worker pattern.
+WASM runs in a Web Worker in browsers, this is optional but highly recommend.
+Every web template should at least suggestion the worker pattern.
---
@@ -66,33 +88,42 @@ package.json # yarn start runs src/index.ts
.env.example # Any required secrets or endpoints
```
-- Use top-level `await`, initialize thread pool at the top: `await initThreadPool();`
+- Use top-level `await`, initialize thread pool at the top:
+ `await initThreadPool();`
- Organize into named async functions, one per feature.
- Use section headers matching tutorial step numbers:
- ```ts
// --- STEP 1: Initialize key provider and cache keys. --- //
```
-- `yarn start` must run successfully without modification (offline features) or with only `.env` filled in (network features)
+- `yarn start` must run successfully without modification (offline features) or
+ with only `.env` filled in (network features)
### Web templates (`template-react-*-ts`)
The wallet adapter has this API here:
-* https://github.com/ProvableHQ/aleo-dev-toolkit/blob/master/packages/aleo-wallet-adaptor/core/src/adapter.ts
-* https://github.com/ProvableHQ/aleo-dev-toolkit/blob/master/packages/aleo-wallet-adaptor/core/src/account.ts
+
+- https://github.com/ProvableHQ/aleo-dev-toolkit/blob/master/packages/aleo-wallet-adaptor/core/src/adapter.ts
+- https://github.com/ProvableHQ/aleo-dev-toolkit/blob/master/packages/aleo-wallet-adaptor/core/src/account.ts
and for web examples, this should be used to do the following.
+
1. Executing transactions (via the `executeTransaction` method)
2. Creating new accounts (via the `createAccount` method)
3. Polling transaction status (via the `transactionStatus` method)
-4. Decrypting ciphertexts from transition inputs and outputs (via the `decrypt` method). Note this does not do arbitrary encryption and decryption schemes, only decryption of transition inputs and outputs.
+4. Decrypting ciphertexts from transition inputs and outputs (via the `decrypt`
+ method). Note this does not do arbitrary encryption and decryption schemes,
+ only decryption of transition inputs and outputs.
5. Record scans via the (via the `requestRecords` method)
6. Executing deployments (via the `executeDeployment` method)
-React environments should look here for context on how to invoke wallets via react: https://github.com/ProvableHQ/aleo-dev-toolkit/blob/master/packages/aleo-wallet-adaptor/react/src/WalletProvider.tsx
+React environments should look here for context on how to invoke wallets via
+react:
+https://github.com/ProvableHQ/aleo-dev-toolkit/blob/master/packages/aleo-wallet-adaptor/react/src/WalletProvider.tsx
-For most create leo app examples (for now) there should be the ability to execute any of the above functions optionally
-via the wallet AND via native SDK methods (where the wallet is preferred).
+For most create leo app examples (for now) there should be the ability to
+execute any of the above functions optionally via the wallet AND via native SDK
+methods (where the wallet is preferred).
```
src/
@@ -103,22 +134,29 @@ vite.config.ts
.env.example
```
-- All `@provablehq/sdk` imports and calls live in `AleoWorker.ts` — never in `App.tsx`
-- Expose worker methods via Comlink; `App.tsx` or any other file calls them like async functions
+- All `@provablehq/sdk` imports and calls live in `AleoWorker.ts` — never in
+ `App.tsx`
+- Expose worker methods via Comlink; `App.tsx` or any other file calls them like
+ async functions
- `initThreadPool()` runs inside the worker, not in the main thread
-- Show loading/progress state in the UI for any proving operation (these take time)
-- Use `aleo-wallet-adapter` for account connection; the SDK worker handles the supplemental operations
+- Show loading/progress state in the UI for any proving operation (these take
+ time)
+- Use `aleo-wallet-adapter` for account connection; the SDK worker handles the
+ supplemental operations
### Both runtimes
-- Imports are always network-specific: `@provablehq/sdk/testnet.js` or `/mainnet.js` — never the bare package
-- Each feature in the bucket gets its own clearly named function — no interleaved logic
-- Error handling must be explicit; ZK errors are opaque, surface them with context:
- ```ts
- } catch (e) {
- throw new KeySynthesisError(`Failed to synthesize keys: ${e}`);
- }
- ```
+- Imports are always network-specific: `@provablehq/sdk/testnet.js` or
+ `/mainnet.js` — never the bare package
+- Each feature in the bucket gets its own clearly named function — no
+ interleaved logic
+- Error handling must be explicit; ZK errors are opaque, surface them with
+ context:
+ ```ts
+ } catch (e) {
+ throw new KeySynthesisError(`Failed to synthesize keys: ${e}`);
+ }
+ ```
---
@@ -127,9 +165,12 @@ vite.config.ts
For each feature in the bucket:
1. Show the **minimal working example** first, then advanced usage
-2. Cover **both node and web** unless the feature is inherently platform-specific
-3. State the **expected output** — what does `yarn start` print? What does the UI show?
-4. Explain **why** non-obvious SDK calls exist (see Code-Doc Correspondence below)
+2. Cover **both node and web** unless the feature is inherently
+ platform-specific
+3. State the **expected output** — what does `yarn start` print? What does the
+ UI show?
+4. Explain **why** non-obvious SDK calls exist (see Code-Doc Correspondence
+ below)
---
@@ -138,46 +179,69 @@ For each feature in the bucket:
Every tutorial follows this shape:
### 1. Overview (1 paragraph)
-What the reader will build. Which features from the bucket are covered. Link to the template.
+
+What the reader will build. Which features from the bucket are covered. Link to
+the template.
### 2. Runtime context (1–2 sentences)
-Why a developer would use the SDK in this runtime for this use case. Reference the framing from the Runtime Context section above. For web tutorials, mention `aleo-wallet-adapter` and its relationship to the SDK.
+
+Why a developer would use the SDK in this runtime for this use case. Reference
+the framing from the Runtime Context section above. For web tutorials, mention
+`aleo-wallet-adapter` and its relationship to the SDK.
### 3. Prerequisites
+
- Node version
- Aleo credits (if network calls are involved)
- Required `.env` values and where to get them
- For web: note that `aleo-wallet-adapter` is needed for account connection
### 4. Concepts
-Plain-English explanation of each feature before showing code. This is where Highlight Areas from the developer's inputs go. Assume only the complexity level specified — don't assume ZK/cryptography knowledge for beginner tutorials.
+
+Plain-English explanation of each feature before showing code. This is where
+Highlight Areas from the developer's inputs go. Assume only the complexity level
+specified — don't assume ZK/cryptography knowledge for beginner tutorials.
### 5. Step-by-step walkthrough
-One section per step, numbered to match the template's section headers. For each step:
+
+One section per step, numbered to match the template's section headers. For each
+step:
+
- What the code does
- **Why** it does it (not just what)
- The relevant code snippet
### 6. Running it
+
Exact commands. Expected output copied from an actual run.
### 7. Next steps
-Links to related templates, the wallet adapter docs (web only), and relevant SDK API docs.
+
+Links to related templates, the wallet adapter docs (web only), and relevant SDK
+API docs.
### Tone
-Third person replacing "you" with appropriate 3rd party nouns, tutorial style: "callers should notice...", "this tells the SDK to...", "here the keys are cached because...". Not API reference style. Not first person.
+
+Third person replacing "you" with appropriate 3rd party nouns, tutorial style:
+"callers should notice...", "this tells the SDK to...", "here the keys are
+cached because...". Not API reference style. Not first person.
---
## Code-Doc Correspondence Rules
-- Step numbers in template comments **must match** step numbers in the tutorial — they are the same document expressed two ways
-- Every non-obvious SDK call in the template requires a "why" explanation in the tutorial. Examples of calls that always need a "why":
- - `initThreadPool()` — why it exists, what happens without it
- - `keyProvider.cacheKeys(...)` — why caching matters (proving key synthesis is slow)
- - `OfflineQuery` — what it replaces and when to use it
- - `buildDeploymentTransaction` vs `deploy` — the distinction between building and submitting
-- **No unexplained magic**: if a call is in the template, it is explained in the tutorial
+- Step numbers in template comments **must match** step numbers in the tutorial
+ — they are the same document expressed two ways
+- Every non-obvious SDK call in the template requires a "why" explanation in the
+ tutorial. Examples of calls that always need a "why":
+ - `initThreadPool()` — why it exists, what happens without it
+ - `keyProvider.cacheKeys(...)` — why caching matters (proving key synthesis
+ is slow)
+ - `OfflineQuery` — what it replaces and when to use it
+ - `buildDeploymentTransaction` vs `deploy` — the distinction between
+ building and submitting
+- **No unexplained magic**: if a call is in the template, it is explained in the
+ tutorial
---
@@ -185,7 +249,8 @@ Third person replacing "you" with appropriate 3rd party nouns, tutorial style: "
Before the tutorial is done:
-- [ ] Template runs with `yarn start` without modification (or only `.env` needed)
+- [ ] Template runs with `yarn start` without modification (or only `.env`
+ needed)
- [ ] Every feature in the bucket is implemented in each target runtime
- [ ] Step numbers align between template comments and tutorial sections
- [ ] Expected output is shown in the tutorial (copied from a real run)
diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md
index 7c9d7409b..bdd0911ec 100644
--- a/.claude/CLAUDE.md
+++ b/.claude/CLAUDE.md
@@ -1,12 +1,15 @@
# CLAUDE.md
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+This file provides guidance to Claude Code (claude.ai/code) when working with
+code in this repository.
## Repository Overview
-Yarn monorepo for the **Provable SDK** — a TypeScript/Rust SDK for building zero-knowledge applications on the Aleo
-blockchain. The SDK re-exports core protocol objects from SnarkVM to allow users to perform operations related to their
-accounts and execute Aleo programs. Main published packages: `@provablehq/sdk` and `@provablehq/wasm` (both v0.9.18).
+Yarn monorepo for the **Provable SDK** — a TypeScript/Rust SDK for building
+zero-knowledge applications on the Aleo blockchain. The SDK re-exports core
+protocol objects from SnarkVM to allow users to perform operations related to
+their accounts and execute Aleo programs. Main published packages:
+`@provablehq/sdk` and `@provablehq/wasm` (both v0.9.18).
**Workspaces:** `sdk`, `wasm`, `create-leo-app`
@@ -46,73 +49,111 @@ yarn test:sdk # cd sdk && yarn test
cd sdk && rimraf tmp && rollup -c rollup.test.js && mocha tmp/account.test.js --timeout 60000
```
-**Test framework:** Mocha + Chai + Sinon. Tests in `sdk/tests/` are bundled by `rollup.test.js` into `sdk/tmp/` before Mocha runs them. Network integration tests (`.integration.ts` files) are skipped by default. Test data lives in `sdk/tests/data/`.
+**Test framework:** Mocha + Chai + Sinon. Tests in `sdk/tests/` are bundled by
+`rollup.test.js` into `sdk/tmp/` before Mocha runs them. Network integration
+tests (`.integration.ts` files) are skipped by default. Test data lives in
+`sdk/tests/data/`.
## Architecture
### Package: `@provablehq/wasm` (`/wasm`)
-Rust crate compiled to WebAssembly via `wasm-bindgen`. Wraps [snarkvm](https://github.com/AleoHQ/snarkvm) to expose Aleo cryptographic primitives to JavaScript. Built by `node build.js` (Rollup + `@wasm-tool/rollup-plugin-rust`). Outputs `dist/testnet/` and `dist/mainnet/`.
+Rust crate compiled to WebAssembly via `wasm-bindgen`. Wraps
+[snarkvm](https://github.com/AleoHQ/snarkvm) to expose Aleo cryptographic
+primitives to JavaScript. Built by `node build.js` (Rollup +
+`@wasm-tool/rollup-plugin-rust`). Outputs `dist/testnet/` and `dist/mainnet/`.
Key Rust modules in `wasm/src/`:
-- `account/` — Account objects PrivateKey, ViewKey, ComputeKey, Address, Signature, Encryptor
-- `programs/manager/` — builds execution proofs, authorizations, proving requests and new aleo program deployments
+
+- `account/` — Account objects PrivateKey, ViewKey, ComputeKey, Address,
+ Signature, Encryptor
+- `programs/manager/` — builds execution proofs, authorizations, proving
+ requests and new aleo program deployments
- `programs/` — Program, execution, keypair, offline_query
- `synthesizer/` — Authorization, ProvingRequest
-- `types/` — Aleo scalar types (Field, Group, Scalar, I8–I128, U8–U128, Boolean) + type re-exports from SnarkVM
+- `types/` — Aleo scalar types (Field, Group, Scalar, I8–I128, U8–U128,
+ Boolean) + type re-exports from SnarkVM
- `algorithms/` — BHP256/512/768/1024, Pedersen64/128, Poseidon2/4/8
- `record/` — RecordPlaintext, RecordCiphertext
- `ledger/` — Transaction, Transition
### Package: `@provablehq/sdk` (`/sdk`)
-TypeScript SDK wrapping `@provablehq/wasm`. Bundled with Rollup into three network variants (`testnet`, `mainnet`, `dynamic`), each with `browser.js` and `node.js` exports.
+TypeScript SDK wrapping `@provablehq/wasm`. Bundled with Rollup into three
+network variants (`testnet`, `mainnet`, `dynamic`), each with `browser.js` and
+`node.js` exports.
Key source files in `sdk/src/`:
-- `wasm.ts` — Re-exports all WASM types; the bridge between Rust types and TS. Uses `%%NETWORK%%` in the import path.
-- `account.ts` — `Account` class: key derivation, signing, ciphertext import/export
-- `network-client.ts` — `AleoNetworkClient`: REST calls to Aleo nodes + DPS integration (JWT auth, encrypted proving)
-- `program-manager.ts` — Orchestrates deploy, execute, transfer; wraps `WasmProgramManager`
-- `record-provider.ts` — `NetworkRecordProvider`: fetching and decrypting user records
-- `record-scanner.ts` — Record scanning service integration (registration, revocation, filtering)
-- `security.ts` — libsodium-based encryption for DPS and RSS (`crypto_box_seal` for Authorization, ProvingRequest, ViewKey)
+
+- `wasm.ts` — Re-exports all WASM types; the bridge between Rust types and TS.
+ Uses `%%NETWORK%%` in the import path.
+- `account.ts` — `Account` class: key derivation, signing, ciphertext
+ import/export
+- `network-client.ts` — `AleoNetworkClient`: REST calls to Aleo nodes + DPS
+ integration (JWT auth, encrypted proving)
+- `program-manager.ts` — Orchestrates deploy, execute, transfer; wraps
+ `WasmProgramManager`
+- `record-provider.ts` — `NetworkRecordProvider`: fetching and decrypting user
+ records
+- `record-scanner.ts` — Record scanning service integration (registration,
+ revocation, filtering)
+- `security.ts` — libsodium-based encryption for DPS and RSS (`crypto_box_seal`
+ for Authorization, ProvingRequest, ViewKey)
- `constants.ts` — Credit program keys, transfer types, timing constants
- `utils.ts` — `retryWithBackoff`, HTTP helpers, environment detection
- `browser.ts` / `node.ts` — Runtime entry points (set up polyfills, re-export)
**Key subdirectories in `sdk/src/`:**
-- `keys/provider/` — `FunctionKeyProvider` interface, `AleoKeyProvider` (memory/network), `OfflineKeyProvider`
+
+- `keys/provider/` — `FunctionKeyProvider` interface, `AleoKeyProvider`
+ (memory/network), `OfflineKeyProvider`
- `keys/keystore/` — Key storage interface and file-based implementation
- `keys/verifier/` — Verifying key interface and memory implementation
-- `models/` — TypeScript types for transactions, deployments, executions, records, DPS, record scanner, plaintext
-- `models/record-scanner/` — Registration, filtering, and result types for the record scanner service
+- `models/` — TypeScript types for transactions, deployments, executions,
+ records, DPS, record scanner, plaintext
+- `models/record-scanner/` — Registration, filtering, and result types for the
+ record scanner service
- `integrations/sealance/` — Sealance Merkle tree integration
### Network Variants & Build System
-`rollup.config.js` builds `testnet` and `mainnet` separately via `@rollup/plugin-replace`, substituting:
-- `%%NETWORK%%` → `testnet` or `mainnet` (used in `wasm.ts` import and test files)
+`rollup.config.js` builds `testnet` and `mainnet` separately via
+`@rollup/plugin-replace`, substituting:
+
+- `%%NETWORK%%` → `testnet` or `mainnet` (used in `wasm.ts` import and test
+ files)
- `%%VERSION%%` → package version
-The `dynamic` variant is **auto-generated** by `buildRuntimes()` in `rollup.config.js` — it writes `dist/dynamic/browser.js` and `dist/dynamic/node.js` that dynamically import either network at runtime via `loadNetwork(name)`. This generation runs before the Rollup export.
+The `dynamic` variant is **auto-generated** by `buildRuntimes()` in
+`rollup.config.js` — it writes `dist/dynamic/browser.js` and
+`dist/dynamic/node.js` that dynamically import either network at runtime via
+`loadNetwork(name)`. This generation runs before the Rollup export.
### Delegated Proving Service (DPS)
-Programs can offload expensive proof generation to a remote prover instead of running locally:
+Programs can offload expensive proof generation to a remote prover instead of
+running locally:
+
1. `ProgramManager` builds an `Authorization` or `ProvingRequest` locally
-2. `security.ts` encrypts proving requests and record scanner registration requests with each respective service's X25519 public key (libsodium `crypto_box_seal`)
-3. `AleoNetworkClient` submits via `DelegatedProvingParams` with optional API key + JWT auth
+2. `security.ts` encrypts proving requests and record scanner registration
+ requests with each respective service's X25519 public key (libsodium
+ `crypto_box_seal`)
+3. `AleoNetworkClient` submits via `DelegatedProvingParams` with optional API
+ key + JWT auth
4. Response contains the completed transaction
-Configure by passing `proverUri` (and optionally `recordScannerUri`) to `AleoNetworkClientOptions`.
+Configure by passing `proverUri` (and optionally `recordScannerUri`) to
+`AleoNetworkClientOptions`.
### Package: `create-leo-app` (`/create-leo-app`)
-Interactive CLI scaffolding (`npm create leo-app`). Templates in `create-leo-app/template-*/`. Built with `unbuild`.
+Interactive CLI scaffolding (`npm create leo-app`). Templates in
+`create-leo-app/template-*/`. Built with `unbuild`.
### Package: `website` (`/website`)
-Demo app at provable.tools. React 19 + Vite + Ant Design + CodeMirror. Not published to npm.
+Demo app at provable.tools. React 19 + Vite + Ant Design + CodeMirror. Not
+published to npm.
## Key Conventions
diff --git a/.claude/commands/wrap-snarkvm.md b/.claude/commands/wrap-snarkvm.md
index 2822692fb..d771685ec 100644
--- a/.claude/commands/wrap-snarkvm.md
+++ b/.claude/commands/wrap-snarkvm.md
@@ -6,11 +6,13 @@ Automates wrapping a SnarkVM type in wasm-bindgen bindings for the Provable SDK.
Ask the user for the following before proceeding. Do not guess.
-1. **SnarkVM type path** — fully-qualified Rust path, e.g. `snarkvm_ledger_block::Transaction`
+1. **SnarkVM type path** — fully-qualified Rust path, e.g.
+ `snarkvm_ledger_block::Transaction`
2. **SnarkVM source** — one of:
- A GitHub branch name, e.g. `staging` (will fetch via `gh api`)
- A local path to a SnarkVM checkout, e.g. `~/dev/snarkvm`
-3. **Wrapper destination** — where the new `.rs` wrapper file should live, e.g. `wasm/src/ledger/transaction.rs`
+3. **Wrapper destination** — where the new `.rs` wrapper file should live, e.g.
+ `wasm/src/ledger/transaction.rs`
4. **Methods to expose** — either "all public methods" or a specific list
---
@@ -18,16 +20,24 @@ Ask the user for the following before proceeding. Do not guess.
## Step 1: Fetch the SnarkVM type definition
**If GitHub branch:**
+
- Derive the file path from the crate name. For example:
- - `snarkvm_ledger_block::Transaction` → crate `snarkvm-ledger-block` → look in `ledger/block/src/`
- - `snarkvm_console::program::Plaintext` → crate `snarkvm-console` → look in `console/src/program/`
-- Use `gh api "repos/ProvableHQ/snarkVM/contents/PATH?ref=BRANCH"` and decode the base64 content
-- If the exact file path is unclear, use `gh api "repos/ProvableHQ/snarkVM/git/trees/BRANCH?recursive=1"` to list the tree and locate the right file
+ - `snarkvm_ledger_block::Transaction` → crate `snarkvm-ledger-block` → look
+ in `ledger/block/src/`
+ - `snarkvm_console::program::Plaintext` → crate `snarkvm-console` → look in
+ `console/src/program/`
+- Use `gh api "repos/ProvableHQ/snarkVM/contents/PATH?ref=BRANCH"` and decode
+ the base64 content
+- If the exact file path is unclear, use
+ `gh api "repos/ProvableHQ/snarkVM/git/trees/BRANCH?recursive=1"` to list the
+ tree and locate the right file
**If local path:**
+
- Read the file directly using the path derived from the crate/module structure
-Read the type definition thoroughly — note all public methods, their signatures, and any trait bounds.
+Read the type definition thoroughly — note all public methods, their signatures,
+and any trait bounds.
---
@@ -35,10 +45,14 @@ Read the type definition thoroughly — note all public methods, their signature
This step is always the same regardless of wrapper destination.
-1. Add the `use` import from the appropriate SnarkVM crate to the existing import block. Match the grouping style — account types together, ledger types together, etc.
-2. Add a `pub type TypeNameNative = TypeName;` alias in the appropriate section.
+1. Add the `use` import from the appropriate SnarkVM crate to the existing
+ import block. Match the grouping style — account types together, ledger types
+ together, etc.
+2. Add a `pub type TypeNameNative = TypeName;` alias in the
+ appropriate section.
Example — adding `Transaction` from `snarkvm_ledger_block`:
+
```rust
// In the use block (already present or add to existing ledger group):
use snarkvm_ledger_block::{..., Transaction};
@@ -47,7 +61,8 @@ use snarkvm_ledger_block::{..., Transaction};
pub type TransactionNative = Transaction;
```
-Do not add a new `use` statement if the crate is already imported — extend the existing one.
+Do not add a new `use` statement if the crate is already imported — extend the
+existing one.
Ensure all imports are in alphabetical order.
@@ -79,7 +94,7 @@ impl TypeName {
// - to_string gets #[wasm_bindgen(js_name = "toString")] and #[allow(clippy::inherent_to_string)]
// - from_str / constructors get #[wasm_bindgen(js_name = "fromString")] etc.
// - Fallible methods return Result — map errors with .map_err(|e| e.to_string())
- // - Methods should have to_string(), from_string(), to_bytes_le(), from_bytes_le(), to_field(), and to_fields(), from_fields(), to_bits_le(), and from_bits_le() if the SnarkVM object implements any of those.
+ // - Methods should have to_string(), from_string(), to_bytes_le(), from_bytes_le(), to_field(), and to_fields(), from_fields(), to_bits_le(), and from_bits_le() if the SnarkVM object implements any of those.
}
// Always generate all four two-way conversions between TypeName and TypeNameNative.
@@ -122,7 +137,8 @@ impl From<&TypeName> for TypeNameNative {
## Step 4: Write wasm bindgen tests to test out any methods that were written.
-Write tests similar to this for records (feel free to read wasm/src/record/record_ciphertext.rs for the object implementation)
+Write tests similar to this for records (feel free to read
+wasm/src/record/record_ciphertext.rs for the object implementation)
```rust
#[cfg(test)]
@@ -301,7 +317,8 @@ mod tests {
## Step 5: Wire up the module
-Find the `mod.rs` (or equivalent) in the parent directory of the wrapper destination and add:
+Find the `mod.rs` (or equivalent) in the parent directory of the wrapper
+destination and add:
```rust
pub mod type_name;
@@ -315,19 +332,22 @@ Match the style of existing entries in that file.
## Step 6: Verify the wasm tests
Run this from the sdk base directory.
+
```bash
yarn test:wasm
```
Fix any errors before declaring done. Common issues:
+
- Missing imports in the wrapper file
- Trait bounds not satisfied (check what traits the native type requires)
-- Method signatures that need adjustment for wasm-bindgen compatibility (e.g. no generic parameters, no lifetimes on return types)
+- Method signatures that need adjustment for wasm-bindgen compatibility (e.g. no
+ generic parameters, no lifetimes on return types)
## Step 7: Write JS tests of the wasm object and export it in `browser.ts`.
-
-Write JS tests of the wasm object and its methods in the JS sdk in the appropriate test file in `sdk/tests/wasm.test.ts`.
+Write JS tests of the wasm object and its methods in the JS sdk in the
+appropriate test file in `sdk/tests/wasm.test.ts`.
An example of how to write such tests are below.
@@ -373,11 +393,14 @@ An example of how to write such tests are below.
};
```
-Verify these tests work by running `yarn build:wasm && yarn build:sdk && yarn test:sdk` from the root of the sdk directory.
+Verify these tests work by running
+`yarn build:wasm && yarn build:sdk && yarn test:sdk` from the root of the sdk
+directory.
## Step 8: Cleanup Run cargo fmt --all
run the following in the `wasm` directory
+
```bash
cargo fmt --all
```
diff --git a/.codecov.yml b/.codecov.yml
index 0516e58a7..2dcf24f24 100644
--- a/.codecov.yml
+++ b/.codecov.yml
@@ -1,5 +1,5 @@
coverage:
- status:
- project:
- default:
- threshold: 4%
+ status:
+ project:
+ default:
+ threshold: 4%
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
index d70564903..d03e9b170 100644
--- a/.github/ISSUE_TEMPLATE.md
+++ b/.github/ISSUE_TEMPLATE.md
@@ -1,3 +1,4 @@
## 👉 [Please follow one of these issue templates](https://github.com/ProvableHQ/sdk/issues/new/choose) 👈
-Note: to keep the backlog clean and actionable, issues may be immediately closed if they do not follow one of the above issue templates.
+Note: to keep the backlog clean and actionable, issues may be immediately closed
+if they do not follow one of the above issue templates.
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 17610f64a..a4ed4c7fc 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,5 +1,7 @@
blank_issues_enabled: true
contact_links:
- - name: ❓ Q&A Technical Support Channel
- url: https://discord.gg/aleo
- about: For quick questions or technical troubleshooting, please ask them on our dedicated Discord channel.
+ - name: ❓ Q&A Technical Support Channel
+ url: https://discord.gg/aleo
+ about:
+ For quick questions or technical troubleshooting, please ask them on
+ our dedicated Discord channel.
diff --git a/.github/ISSUE_TEMPLATE/documentation.md b/.github/ISSUE_TEMPLATE/documentation.md
index 1198d2720..023620cae 100644
--- a/.github/ISSUE_TEMPLATE/documentation.md
+++ b/.github/ISSUE_TEMPLATE/documentation.md
@@ -2,7 +2,7 @@
name: 📚 Documentation
about: Report an issue related to documentation
title: "[Docs]"
-labels: 'documentation'
+labels: "documentation"
---
## 📚 Documentation
diff --git a/.github/ISSUE_TEMPLATE/feature.md b/.github/ISSUE_TEMPLATE/feature.md
index e348f96f9..12db88495 100644
--- a/.github/ISSUE_TEMPLATE/feature.md
+++ b/.github/ISSUE_TEMPLATE/feature.md
@@ -1,5 +1,5 @@
---
-name: 🚀 Feature
+name: 🚀 Feature
about: Submit a new feature request
title: "[Feature]"
labels: feature
@@ -18,7 +18,7 @@ labels: feature
@@ -33,4 +33,5 @@ labels: feature
How should this feature be implemented?
-->
-**Are you willing to open a pull request?** (See [CONTRIBUTING](../../CONTRIBUTING.md))
+**Are you willing to open a pull request?** (See
+[CONTRIBUTING](../../CONTRIBUTING.md))
diff --git a/.github/ISSUE_TEMPLATE/proposal.md b/.github/ISSUE_TEMPLATE/proposal.md
index b1baeb9a6..dc1ff1a48 100644
--- a/.github/ISSUE_TEMPLATE/proposal.md
+++ b/.github/ISSUE_TEMPLATE/proposal.md
@@ -2,7 +2,7 @@
name: 💥 Proposal
about: Propose a non-trivial change to the Provable SDK
title: "[Proposal]"
-labels: 'proposal'
+labels: "proposal"
---
## 💥 Proposal
diff --git a/.github/actions/setup-rust/action.yml b/.github/actions/setup-rust/action.yml
index c7366e327..b80366298 100644
--- a/.github/actions/setup-rust/action.yml
+++ b/.github/actions/setup-rust/action.yml
@@ -1,17 +1,17 @@
name: Setup Rust
description: Sets up Rust
runs:
- using: "composite"
- steps:
- - uses: actions/cache@v4
- with:
- path: |
- ~/.cargo/registry
- ~/.cargo/git
- target
- key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
+ using: "composite"
+ steps:
+ - uses: actions/cache@v4
+ with:
+ path: |
+ ~/.cargo/registry
+ ~/.cargo/git
+ target
+ key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
- - name: Initialize Rustup
- shell: bash
- run: |
- rustup show
+ - name: Initialize Rustup
+ shell: bash
+ run: |
+ rustup show
diff --git a/.github/actions/setup-yarn/action.yml b/.github/actions/setup-yarn/action.yml
index 47bf3340b..697ab5052 100644
--- a/.github/actions/setup-yarn/action.yml
+++ b/.github/actions/setup-yarn/action.yml
@@ -1,13 +1,13 @@
name: Setup Yarn
description: Sets up Yarn
runs:
- using: "composite"
- steps:
- - uses: actions/setup-node@v4
- with:
- cache: 'yarn'
+ using: "composite"
+ steps:
+ - uses: actions/setup-node@v4
+ with:
+ cache: "yarn"
- - name: yarn install
- shell: bash
- run: |
- yarn install --immutable --check-cache
+ - name: yarn install
+ shell: bash
+ run: |
+ yarn install --immutable --check-cache
diff --git a/.github/actions/use-build/action.yml b/.github/actions/use-build/action.yml
index 6f7521d98..ea0eb4cc0 100644
--- a/.github/actions/use-build/action.yml
+++ b/.github/actions/use-build/action.yml
@@ -1,9 +1,9 @@
name: Use build
description: Uses the build artifacts
runs:
- using: "composite"
- steps:
- - name: Download build
- uses: actions/download-artifact@v4
- with:
- name: build
+ using: "composite"
+ steps:
+ - name: Download build
+ uses: actions/download-artifact@v4
+ with:
+ name: build
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
index 6b17bb24c..168d35b27 100644
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -1,56 +1,56 @@
version: 2
updates:
-- package-ecosystem: cargo
- directory: "/"
- schedule:
- interval: daily
- time: "10:00"
- open-pull-requests-limit: 10
- ignore:
- - dependency-name: wiremock
- versions:
- - 0.5.2
- - dependency-name: wasm-bindgen
- versions:
- - 0.2.71
- - 0.2.72
- - dependency-name: snarkvm-utilities
- versions:
- - 0.0.3
- - 0.0.4
- - 0.0.6
- - 0.2.0
- - 0.2.1
- - dependency-name: serde_json
- versions:
- - 1.0.63
- - 1.0.64
- - dependency-name: self_update
- versions:
- - 0.24.0
- - dependency-name: thiserror
- versions:
- - 1.0.24
- - dependency-name: snarkvm-storage
- versions:
- - 0.0.3
- - 0.0.4
- - dependency-name: snarkvm-dpc
- versions:
- - 0.0.3
- - 0.0.4
- - dependency-name: snarkvm-errors
- versions:
- - 0.0.3
- - 0.0.4
- - dependency-name: rand_chacha
- versions:
- - 0.3.0
- - dependency-name: snarkvm-objects
- versions:
- - 0.0.3
- - 0.0.4
- - dependency-name: snarkvm-models
- versions:
- - 0.0.3
- - 0.0.4
+ - package-ecosystem: cargo
+ directory: "/"
+ schedule:
+ interval: daily
+ time: "10:00"
+ open-pull-requests-limit: 10
+ ignore:
+ - dependency-name: wiremock
+ versions:
+ - 0.5.2
+ - dependency-name: wasm-bindgen
+ versions:
+ - 0.2.71
+ - 0.2.72
+ - dependency-name: snarkvm-utilities
+ versions:
+ - 0.0.3
+ - 0.0.4
+ - 0.0.6
+ - 0.2.0
+ - 0.2.1
+ - dependency-name: serde_json
+ versions:
+ - 1.0.63
+ - 1.0.64
+ - dependency-name: self_update
+ versions:
+ - 0.24.0
+ - dependency-name: thiserror
+ versions:
+ - 1.0.24
+ - dependency-name: snarkvm-storage
+ versions:
+ - 0.0.3
+ - 0.0.4
+ - dependency-name: snarkvm-dpc
+ versions:
+ - 0.0.3
+ - 0.0.4
+ - dependency-name: snarkvm-errors
+ versions:
+ - 0.0.3
+ - 0.0.4
+ - dependency-name: rand_chacha
+ versions:
+ - 0.3.0
+ - dependency-name: snarkvm-objects
+ versions:
+ - 0.0.3
+ - 0.0.4
+ - dependency-name: snarkvm-models
+ versions:
+ - 0.0.3
+ - 0.0.4
diff --git a/.github/workflows/sdk.yml b/.github/workflows/sdk.yml
index d604d6476..3119811b1 100644
--- a/.github/workflows/sdk.yml
+++ b/.github/workflows/sdk.yml
@@ -1,247 +1,246 @@
name: SDK
on:
- pull_request:
- push:
- branches:
- - mainnet
- - testnet
+ pull_request:
+ push:
+ branches:
+ - mainnet
+ - testnet
env:
- CARGO_TERM_COLOR: always
- PUZZLE_PK: ${{ secrets.PUZZLE_PK }}
- PUZZLE_VK: ${{ secrets.PUZZLE_VK }}
- RECORD_SCANNER_URL: ${{ secrets.RECORD_SCANNER_URL }}
- KONG_API_KEY: ${{ secrets.ALEO_DPS_API_KEY }}
- CONSUMER_ID: ${{ secrets.ALEO_CONSUMER_ID }}
-
+ CARGO_TERM_COLOR: always
+ PUZZLE_PK: ${{ secrets.PUZZLE_PK }}
+ PUZZLE_VK: ${{ secrets.PUZZLE_VK }}
+ RECORD_SCANNER_URL: ${{ secrets.RECORD_SCANNER_URL }}
+ KONG_API_KEY: ${{ secrets.ALEO_DPS_API_KEY }}
+ CONSUMER_ID: ${{ secrets.ALEO_CONSUMER_ID }}
jobs:
- build:
- name: build
- runs-on: ubuntu-latest-m
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/setup-rust
-
- - run: |
- yarn build:all
-
- - name: Upload build artifacts
- uses: actions/upload-artifact@v4
- with:
- name: build
- path: |
- sdk/dist/
- wasm/dist/
- create-leo-app/dist/
-
-
- test-wasm:
- name: test wasm
- runs-on: ubuntu-latest-m
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
-
- - run: |
- yarn test:wasm
-
-
- test-sdk:
- name: test sdk
- runs-on: ubuntu-latest
- needs: build
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/use-build
-
- - run: |
- yarn test:sdk
-
-
- e2e:
- name: "e2e"
- runs-on: ubuntu-latest-m
- needs: build
- strategy:
- fail-fast: false
- matrix:
- network: [testnet, mainnet, dynamic]
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/use-build
-
- - working-directory: e2e/${{ matrix.network }}
- run: |
- yarn start
-
-
- create-leo-app-cli:
- name: "create-leo-app CLI"
- runs-on: ubuntu-latest-m
- needs: build
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/use-build
-
- - working-directory: create-leo-app
- run: |
- npm i -D tsx
- npx tsx src/index.ts test-app --template react-leo
-
-
- create-leo-app-build:
- name: "create-leo-app build"
- runs-on: ubuntu-latest-m
- needs: build
- strategy:
- fail-fast: false
- matrix:
- template:
- - extension
- - nextjs-ts
- - offline-public-transaction-ts
- - react-credits-aleo-functions-ts
- - react-leo
- #- react-managed-worker
- - react-ts
- - vanilla
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/use-build
-
- - working-directory: create-leo-app/template-${{ matrix.template }}
- run: |
- yarn build
-
-
- create-leo-app-run:
- name: "create-leo-app run"
- runs-on: ubuntu-latest-m
- needs: build
- strategy:
- fail-fast: false
- matrix:
- template:
- - node
- - node-credits-aleo-functions-ts
- - node-ts
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/use-build
-
- - working-directory: create-leo-app/template-${{ matrix.template }}
- run: |
- yarn start
-
-
- create-leo-app-loyalty-program-local:
- name: "create-leo-app loyalty-program (local)"
- runs-on: ubuntu-latest-m
- needs: build
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/use-build
-
- - working-directory: create-leo-app/template-node-loyalty-program-ts
- run: |
- yarn local
-
-
- create-leo-app-loyalty-program-delegated:
- name: "create-leo-app loyalty-program (delegated + scanner)"
- runs-on: ubuntu-latest-m
- needs: build
- env:
- # Consumer ID (used for both DPS and RSS)
- ALEO_CONSUMER_ID: ${{ secrets.ALEO_CONSUMER_ID }}
- # DPS configuration
- ALEO_DPS_URL: https://api.provable.com/prove/testnet
- ALEO_DPS_API_KEY: ${{ secrets.ALEO_DPS_API_KEY }}
- # RSS configuration
- ALEO_RSS_URL: https://api.provable.com/scanner
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/use-build
-
- - name: Run delegated mode (creates on-chain records)
- working-directory: create-leo-app/template-node-loyalty-program-ts
- run: |
- yarn delegated
-
- - name: Run scanner mode (finds on-chain records)
- working-directory: create-leo-app/template-node-loyalty-program-ts
- run: |
- yarn scanner
-
-
- clippy:
- name: "clippy"
- runs-on: ubuntu-latest
- strategy:
- fail-fast: false
- matrix:
- network: [testnet, mainnet]
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-rust
-
- - name: "cargo clippy"
- working-directory: wasm
- run: |
- cargo clippy --features ${{ matrix.network }}
-
-
- rustfmt:
- name: "rustfmt"
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-rust
-
- - name: "cargo fmt"
- working-directory: wasm
- run: |
- cargo fmt --all --check
-
-
- website:
- name: website
- runs-on: ubuntu-latest
- needs: build
-
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/use-build
-
- - name: Build Website
- working-directory: website
- run: |
- yarn build
-
- - name: Test Deploy
- id: unmodified
- uses: JamesIves/github-pages-deploy-action@v4
- with:
- token: ${{ secrets.GITHUB_TOKEN }}
- branch: gh-pages
- folder: website/dist
- clean-exclude: '["dev"]'
- dry-run: true
-
- - name: Check step output
- run: |
- [[ \
- ${{steps.unmodified.outputs.deployment-status}} = skipped || \
- ${{steps.unmodified.outputs.deployment-status}} = success \
- ]]
+ build:
+ name: build
+ runs-on: ubuntu-latest-m
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/setup-rust
+
+ - run: |
+ yarn build:all
+
+ - name: Upload build artifacts
+ uses: actions/upload-artifact@v4
+ with:
+ name: build
+ path: |
+ sdk/dist/
+ wasm/dist/
+ create-leo-app/dist/
+
+ test-wasm:
+ name: test wasm
+ runs-on: ubuntu-latest-m
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+
+ - run: |
+ yarn test:wasm
+
+ test-sdk:
+ name: test sdk
+ runs-on: ubuntu-latest
+ needs: build
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/use-build
+
+ - run: |
+ yarn test:sdk
+
+ e2e:
+ name: "e2e"
+ runs-on: ubuntu-latest-m
+ needs: build
+ strategy:
+ fail-fast: false
+ matrix:
+ network: [testnet, mainnet, dynamic]
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/use-build
+
+ - working-directory: e2e/${{ matrix.network }}
+ run: |
+ yarn start
+
+ create-leo-app-cli:
+ name: "create-leo-app CLI"
+ runs-on: ubuntu-latest-m
+ needs: build
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/use-build
+
+ - working-directory: create-leo-app
+ run: |
+ npm i -D tsx
+ npx tsx src/index.ts test-app --template react-leo
+
+ create-leo-app-build:
+ name: "create-leo-app build"
+ runs-on: ubuntu-latest-m
+ needs: build
+ strategy:
+ fail-fast: false
+ matrix:
+ template:
+ - extension
+ - nextjs-ts
+ - offline-public-transaction-ts
+ - react-credits-aleo-functions-ts
+ - react-leo
+ #- react-managed-worker
+ - react-ts
+ - vanilla
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/use-build
+
+ - working-directory: create-leo-app/template-${{ matrix.template }}
+ run: |
+ yarn build
+
+ create-leo-app-run:
+ name: "create-leo-app run"
+ runs-on: ubuntu-latest-m
+ needs: build
+ strategy:
+ fail-fast: false
+ matrix:
+ template:
+ - node
+ - node-credits-aleo-functions-ts
+ - node-ts
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/use-build
+
+ - working-directory: create-leo-app/template-${{ matrix.template }}
+ run: |
+ yarn start
+
+ create-leo-app-loyalty-program-local:
+ name: "create-leo-app loyalty-program (local)"
+ runs-on: ubuntu-latest-m
+ needs: build
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/use-build
+
+ - working-directory: create-leo-app/template-node-loyalty-program-ts
+ run: |
+ yarn local
+
+ create-leo-app-loyalty-program-delegated:
+ name: "create-leo-app loyalty-program (delegated + scanner)"
+ runs-on: ubuntu-latest-m
+ needs: build
+ env:
+ # Consumer ID (used for both DPS and RSS)
+ ALEO_CONSUMER_ID: ${{ secrets.ALEO_CONSUMER_ID }}
+ # DPS configuration
+ ALEO_DPS_URL: https://api.provable.com/prove/testnet
+ ALEO_DPS_API_KEY: ${{ secrets.ALEO_DPS_API_KEY }}
+ # RSS configuration
+ ALEO_RSS_URL: https://api.provable.com/scanner
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/use-build
+
+ - name: Run delegated mode (creates on-chain records)
+ working-directory: create-leo-app/template-node-loyalty-program-ts
+ run: |
+ yarn delegated
+
+ - name: Run scanner mode (finds on-chain records)
+ working-directory: create-leo-app/template-node-loyalty-program-ts
+ run: |
+ yarn scanner
+
+ clippy:
+ name: "clippy"
+ runs-on: ubuntu-latest
+ strategy:
+ fail-fast: false
+ matrix:
+ network: [testnet, mainnet]
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-rust
+
+ - name: "cargo clippy"
+ working-directory: wasm
+ run: |
+ cargo clippy --features ${{ matrix.network }}
+
+ rustfmt:
+ name: "rustfmt"
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-rust
+
+ - name: "cargo fmt"
+ working-directory: wasm
+ run: |
+ cargo fmt --all --check
+
+ prettier:
+ name: "prettier"
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+
+ - name: "prettier --check"
+ run: |
+ yarn lint
+
+ website:
+ name: website
+ runs-on: ubuntu-latest
+ needs: build
+
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/use-build
+
+ - name: Build Website
+ working-directory: website
+ run: |
+ yarn build
+
+ - name: Test Deploy
+ id: unmodified
+ uses: JamesIves/github-pages-deploy-action@v4
+ with:
+ token: ${{ secrets.GITHUB_TOKEN }}
+ branch: gh-pages
+ folder: website/dist
+ clean-exclude: '["dev"]'
+ dry-run: true
+
+ - name: Check step output
+ run: |
+ [[ \
+ ${{steps.unmodified.outputs.deployment-status}} = skipped || \
+ ${{steps.unmodified.outputs.deployment-status}} = success \
+ ]]
diff --git a/.github/workflows/staging-website.yml b/.github/workflows/staging-website.yml
index 81e147f9c..de79b738a 100644
--- a/.github/workflows/staging-website.yml
+++ b/.github/workflows/staging-website.yml
@@ -1,38 +1,38 @@
name: Staging Website Deploy
on:
- push:
- branches:
- - staging
+ push:
+ branches:
+ - staging
jobs:
- deploy:
- name: SDK Website
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/setup-rust
+ deploy:
+ name: SDK Website
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/setup-rust
- - name: Install and Build
- run: |
- yarn build:all
- cd website
- yarn build
- env:
- CI: ""
+ - name: Install and Build
+ run: |
+ yarn build:all
+ cd website
+ yarn build
+ env:
+ CI: ""
- - name: Deploy
- id: modified
- uses: JamesIves/github-pages-deploy-action@v4
- with:
- token: ${{ secrets.GITHUB_TOKEN }}
- branch: staging.provable.tools
- folder: website/dist
- clean-exclude: '["dev"]'
+ - name: Deploy
+ id: modified
+ uses: JamesIves/github-pages-deploy-action@v4
+ with:
+ token: ${{ secrets.GITHUB_TOKEN }}
+ branch: staging.provable.tools
+ folder: website/dist
+ clean-exclude: '["dev"]'
- - name: Check step output
- run: |
- [[ \
- ${{steps.modified.outputs.deployment-status}} = skipped || \
- ${{steps.modified.outputs.deployment-status}} = success \
- ]]
+ - name: Check step output
+ run: |
+ [[ \
+ ${{steps.modified.outputs.deployment-status}} = skipped || \
+ ${{steps.modified.outputs.deployment-status}} = success \
+ ]]
diff --git a/.github/workflows/update-snarkvm.yml b/.github/workflows/update-snarkvm.yml
index 1dbddbcd2..c5fcbf6f6 100644
--- a/.github/workflows/update-snarkvm.yml
+++ b/.github/workflows/update-snarkvm.yml
@@ -1,150 +1,150 @@
name: Update snarkVM dependency
on:
- schedule:
- # Run once every day at midnight (UTC)
- - cron: '0 0 * * *'
- push:
- branches:
- - 'ci/snarkvm-update'
+ schedule:
+ # Run once every day at midnight (UTC)
+ - cron: "0 0 * * *"
+ push:
+ branches:
+ - "ci/snarkvm-update"
env:
- RUST_BACKTRACE: 1
+ RUST_BACKTRACE: 1
jobs:
- update-snarkvm-staging:
- name: Update snarkVM to latest staging
- runs-on: ubuntu-22.04
- permissions:
- contents: write
- pull-requests: write
- steps:
- - name: Checkout SDK
- uses: actions/checkout@v5
- with:
- ref: mainnet
- token: ${{ secrets.GITHUB_TOKEN }}
-
- - name: Get current snarkVM commit from Cargo.toml
- id: current-commit
- run: |
- # Extract the first snarkVM rev found in the Cargo.toml
- CURRENT_COMMIT=$(grep -E 'snarkvm-[a-zA-Z0-9_-]+ = .*rev\s*=' wasm/Cargo.toml | head -n 1 | sed -E 's/.*rev\s*=\s*"([a-f0-9]+)".*/\1/')
- echo "Current snarkVM commit: $CURRENT_COMMIT"
- echo "current_commit=$CURRENT_COMMIT" >> $GITHUB_OUTPUT
-
- - name: Get latest snarkVM staging commit
- id: snarkvm-commit
- uses: actions/github-script@v7
- with:
- script: |
- // Get the latest commit hash from snarkVM staging branch
- const { data: branch } = await github.rest.repos.getBranch({
- owner: 'ProvableHQ',
- repo: 'snarkVM',
- branch: 'staging'
- });
-
- const latestCommit = branch.commit.sha;
- console.log('Latest snarkVM staging commit:', latestCommit);
- core.setOutput('latest_commit', latestCommit);
- core.setOutput('update_needed', 'true');
-
- - name: Setup Git
- if: steps.snarkvm-commit.outputs.update_needed == 'true'
- run: |
- git config --global user.name "github-actions[bot]"
- git config --global user.email "github-actions[bot]@users.noreply.github.com"
-
- - name: Create new update-snarkvm-staging branch from staging
- if: steps.snarkvm-commit.outputs.update_needed == 'true'
- run: |
- git fetch origin staging:staging
- # Always create a fresh branch from staging
- echo "Creating new update-snarkvm-staging branch from staging"
- git checkout -B update-snarkvm-staging origin/staging
- echo "Created fresh update-snarkvm-staging branch from staging"
-
- - name: Update snarkVM dependency
- if: steps.snarkvm-commit.outputs.update_needed == 'true'
- run: |
- # Validate the commit hash format (should be 40 chars hex or 7+ chars)
- LATEST_COMMIT="${{ steps.snarkvm-commit.outputs.latest_commit }}"
- if [[ ! "$LATEST_COMMIT" =~ ^[a-f0-9]{7,40}$ ]]; then
- echo "Error: Invalid commit hash format: $LATEST_COMMIT"
- exit 1
- fi
-
- # First, update the rev in Cargo.toml to point to the new commit
- cd wasm
- cargo add snarkvm-algorithms --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
- cargo add snarkvm-circuit-network --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
- cargo add snarkvm-console --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
- cargo add snarkvm-ledger-block --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
- cargo add snarkvm-ledger-query --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
- cargo add snarkvm-ledger-store --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
- cargo add snarkvm-parameters --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
- cargo add snarkvm-synthesizer-program --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
- cargo add snarkvm-synthesizer --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
- cargo add snarkvm-wasm --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
-
- echo "✅ Successfully updated snarkVM dependency to $LATEST_COMMIT"
-
- - name: Commit and push changes
- if: steps.snarkvm-commit.outputs.update_needed == 'true'
- run: |
- git add wasm/Cargo.toml wasm/Cargo.lock
- git commit --no-verify -m "Update snarkVM to latest staging commit ${{ steps.snarkvm-commit.outputs.latest_commit }}
-
- Previous commit: ${{ steps.snarkvm-commit.outputs.current_commit }}
- Latest commit: ${{ steps.snarkvm-commit.outputs.latest_commit }}
-
- This update was performed automatically by the snarkVM update workflow."
-
- # Make sure the remote branch exists and is up to date
- git fetch origin update-snarkvm-staging || true
-
- # Push forcefully (safe because only CI touches this branch)
- git push --force origin update-snarkvm-staging
-
- - name: Create or update PR
- if: steps.snarkvm-commit.outputs.update_needed == 'true'
- uses: actions/github-script@v7
- with:
- script: |
- // Check if a PR already exists from update-snarkvm-staging to staging
- const { data: prs } = await github.rest.pulls.list({
- owner: 'ProvableHQ',
- repo: 'sdk',
- head: 'ProvableHQ:update-snarkvm-staging',
- base: 'staging',
- state: 'open'
- });
-
- if (prs.length === 0) {
- // No PR exists, create one
- const { data: pr } = await github.rest.pulls.create({
- owner: 'ProvableHQ',
- repo: 'sdk',
- title: 'Update snarkVM to latest staging commit',
- head: 'update-snarkvm-staging',
- base: 'staging',
- body: 'This PR updates the snarkVM dependency to track the latest staging commit.\n\nLatest commit: ${{ steps.snarkvm-commit.outputs.latest_commit }}\nPrevious commit: ${{ steps.snarkvm-commit.outputs.current_commit }}\n\nThis PR was created automatically by the snarkVM update workflow.'
- });
- console.log(`Created PR #${pr.number}: ${pr.html_url}`);
- } else {
- console.log(`PR already exists: ${prs[0].html_url}`);
- }
-
- - name: Summary
- if: always()
- run: |
- echo "## Workflow Summary (staging)" >> $GITHUB_STEP_SUMMARY
- echo "- Current snarkVM commit: ${{ steps.snarkvm-commit.outputs.current_commit }}" >> $GITHUB_STEP_SUMMARY
- echo "- Latest snarkVM commit: ${{ steps.snarkvm-commit.outputs.latest_commit }}" >> $GITHUB_STEP_SUMMARY
- echo "- Update needed: ${{ steps.snarkvm-commit.outputs.update_needed }}" >> $GITHUB_STEP_SUMMARY
- if [ "${{ steps.snarkvm-commit.outputs.update_needed }}" = "true" ]; then
- echo "- ✅ snarkVM dependency updated successfully" >> $GITHUB_STEP_SUMMARY
- else
- echo "- ℹ️ No update required" >> $GITHUB_STEP_SUMMARY
- fi
+ update-snarkvm-staging:
+ name: Update snarkVM to latest staging
+ runs-on: ubuntu-22.04
+ permissions:
+ contents: write
+ pull-requests: write
+ steps:
+ - name: Checkout SDK
+ uses: actions/checkout@v5
+ with:
+ ref: mainnet
+ token: ${{ secrets.GITHUB_TOKEN }}
+
+ - name: Get current snarkVM commit from Cargo.toml
+ id: current-commit
+ run: |
+ # Extract the first snarkVM rev found in the Cargo.toml
+ CURRENT_COMMIT=$(grep -E 'snarkvm-[a-zA-Z0-9_-]+ = .*rev\s*=' wasm/Cargo.toml | head -n 1 | sed -E 's/.*rev\s*=\s*"([a-f0-9]+)".*/\1/')
+ echo "Current snarkVM commit: $CURRENT_COMMIT"
+ echo "current_commit=$CURRENT_COMMIT" >> $GITHUB_OUTPUT
+
+ - name: Get latest snarkVM staging commit
+ id: snarkvm-commit
+ uses: actions/github-script@v7
+ with:
+ script: |
+ // Get the latest commit hash from snarkVM staging branch
+ const { data: branch } = await github.rest.repos.getBranch({
+ owner: 'ProvableHQ',
+ repo: 'snarkVM',
+ branch: 'staging'
+ });
+
+ const latestCommit = branch.commit.sha;
+ console.log('Latest snarkVM staging commit:', latestCommit);
+ core.setOutput('latest_commit', latestCommit);
+ core.setOutput('update_needed', 'true');
+
+ - name: Setup Git
+ if: steps.snarkvm-commit.outputs.update_needed == 'true'
+ run: |
+ git config --global user.name "github-actions[bot]"
+ git config --global user.email "github-actions[bot]@users.noreply.github.com"
+
+ - name: Create new update-snarkvm-staging branch from staging
+ if: steps.snarkvm-commit.outputs.update_needed == 'true'
+ run: |
+ git fetch origin staging:staging
+ # Always create a fresh branch from staging
+ echo "Creating new update-snarkvm-staging branch from staging"
+ git checkout -B update-snarkvm-staging origin/staging
+ echo "Created fresh update-snarkvm-staging branch from staging"
+
+ - name: Update snarkVM dependency
+ if: steps.snarkvm-commit.outputs.update_needed == 'true'
+ run: |
+ # Validate the commit hash format (should be 40 chars hex or 7+ chars)
+ LATEST_COMMIT="${{ steps.snarkvm-commit.outputs.latest_commit }}"
+ if [[ ! "$LATEST_COMMIT" =~ ^[a-f0-9]{7,40}$ ]]; then
+ echo "Error: Invalid commit hash format: $LATEST_COMMIT"
+ exit 1
+ fi
+
+ # First, update the rev in Cargo.toml to point to the new commit
+ cd wasm
+ cargo add snarkvm-algorithms --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
+ cargo add snarkvm-circuit-network --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
+ cargo add snarkvm-console --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
+ cargo add snarkvm-ledger-block --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
+ cargo add snarkvm-ledger-query --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
+ cargo add snarkvm-ledger-store --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
+ cargo add snarkvm-parameters --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
+ cargo add snarkvm-synthesizer-program --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
+ cargo add snarkvm-synthesizer --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
+ cargo add snarkvm-wasm --git https://github.com/ProvableHQ/snarkVM --rev $LATEST_COMMIT
+
+ echo "✅ Successfully updated snarkVM dependency to $LATEST_COMMIT"
+
+ - name: Commit and push changes
+ if: steps.snarkvm-commit.outputs.update_needed == 'true'
+ run: |
+ git add wasm/Cargo.toml wasm/Cargo.lock
+ git commit --no-verify -m "Update snarkVM to latest staging commit ${{ steps.snarkvm-commit.outputs.latest_commit }}
+
+ Previous commit: ${{ steps.snarkvm-commit.outputs.current_commit }}
+ Latest commit: ${{ steps.snarkvm-commit.outputs.latest_commit }}
+
+ This update was performed automatically by the snarkVM update workflow."
+
+ # Make sure the remote branch exists and is up to date
+ git fetch origin update-snarkvm-staging || true
+
+ # Push forcefully (safe because only CI touches this branch)
+ git push --force origin update-snarkvm-staging
+
+ - name: Create or update PR
+ if: steps.snarkvm-commit.outputs.update_needed == 'true'
+ uses: actions/github-script@v7
+ with:
+ script: |
+ // Check if a PR already exists from update-snarkvm-staging to staging
+ const { data: prs } = await github.rest.pulls.list({
+ owner: 'ProvableHQ',
+ repo: 'sdk',
+ head: 'ProvableHQ:update-snarkvm-staging',
+ base: 'staging',
+ state: 'open'
+ });
+
+ if (prs.length === 0) {
+ // No PR exists, create one
+ const { data: pr } = await github.rest.pulls.create({
+ owner: 'ProvableHQ',
+ repo: 'sdk',
+ title: 'Update snarkVM to latest staging commit',
+ head: 'update-snarkvm-staging',
+ base: 'staging',
+ body: 'This PR updates the snarkVM dependency to track the latest staging commit.\n\nLatest commit: ${{ steps.snarkvm-commit.outputs.latest_commit }}\nPrevious commit: ${{ steps.snarkvm-commit.outputs.current_commit }}\n\nThis PR was created automatically by the snarkVM update workflow.'
+ });
+ console.log(`Created PR #${pr.number}: ${pr.html_url}`);
+ } else {
+ console.log(`PR already exists: ${prs[0].html_url}`);
+ }
+
+ - name: Summary
+ if: always()
+ run: |
+ echo "## Workflow Summary (staging)" >> $GITHUB_STEP_SUMMARY
+ echo "- Current snarkVM commit: ${{ steps.snarkvm-commit.outputs.current_commit }}" >> $GITHUB_STEP_SUMMARY
+ echo "- Latest snarkVM commit: ${{ steps.snarkvm-commit.outputs.latest_commit }}" >> $GITHUB_STEP_SUMMARY
+ echo "- Update needed: ${{ steps.snarkvm-commit.outputs.update_needed }}" >> $GITHUB_STEP_SUMMARY
+ if [ "${{ steps.snarkvm-commit.outputs.update_needed }}" = "true" ]; then
+ echo "- ✅ snarkVM dependency updated successfully" >> $GITHUB_STEP_SUMMARY
+ else
+ echo "- ℹ️ No update required" >> $GITHUB_STEP_SUMMARY
+ fi
diff --git a/.github/workflows/website.yml b/.github/workflows/website.yml
index aff78e453..023797bf9 100644
--- a/.github/workflows/website.yml
+++ b/.github/workflows/website.yml
@@ -1,38 +1,38 @@
name: Website
on:
- push:
- branches:
- - mainnet
+ push:
+ branches:
+ - mainnet
jobs:
- deploy:
- name: SDK Website
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v4
- - uses: ./.github/actions/setup-yarn
- - uses: ./.github/actions/setup-rust
+ deploy:
+ name: SDK Website
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v4
+ - uses: ./.github/actions/setup-yarn
+ - uses: ./.github/actions/setup-rust
- - name: Install and Build
- run: |
- yarn build:all
- cd website
- yarn build
- env:
- CI: ""
+ - name: Install and Build
+ run: |
+ yarn build:all
+ cd website
+ yarn build
+ env:
+ CI: ""
- - name: Deploy
- id: modified
- uses: JamesIves/github-pages-deploy-action@v4
- with:
- token: ${{ secrets.GITHUB_TOKEN }}
- branch: gh-pages
- folder: website/dist
- clean-exclude: '["dev"]'
+ - name: Deploy
+ id: modified
+ uses: JamesIves/github-pages-deploy-action@v4
+ with:
+ token: ${{ secrets.GITHUB_TOKEN }}
+ branch: gh-pages
+ folder: website/dist
+ clean-exclude: '["dev"]'
- - name: Check step output
- run: |
- [[ \
- ${{steps.modified.outputs.deployment-status}} = skipped || \
- ${{steps.modified.outputs.deployment-status}} = success \
- ]]
+ - name: Check step output
+ run: |
+ [[ \
+ ${{steps.modified.outputs.deployment-status}} = skipped || \
+ ${{steps.modified.outputs.deployment-status}} = success \
+ ]]
diff --git a/.prettierignore b/.prettierignore
new file mode 100644
index 000000000..58ccb2d35
--- /dev/null
+++ b/.prettierignore
@@ -0,0 +1 @@
+docs/api_reference/
diff --git a/LICENSE.md b/LICENSE.md
index b95c626e2..bea2ca68d 100644
--- a/LICENSE.md
+++ b/LICENSE.md
@@ -1,5 +1,4 @@
-GNU General Public License
-==========================
+# GNU General Public License
Version 3, 29 June 2007
@@ -10,59 +9,62 @@ document, but changing it is not allowed.
## Preamble
-The GNU General Public License is a free, copyleft license for software and other
-kinds of works.
-
-The licenses for most software and other practical works are designed to take away
-your freedom to share and change the works. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change all versions of a
-program--to make sure it remains free software for all its users. We, the Free
-Software Foundation, use the GNU General Public License for most of our software; it
-applies also to any other work released this way by its authors. You can apply it to
-your programs, too.
-
-When we speak of free software, we are referring to freedom, not price. Our General
-Public Licenses are designed to make sure that you have the freedom to distribute
-copies of free software (and charge for them if you wish), that you receive source
-code or can get it if you want it, that you can change the software or use pieces of
-it in new free programs, and that you know you can do these things.
-
-To protect your rights, we need to prevent others from denying you these rights or
-asking you to surrender the rights. Therefore, you have certain responsibilities if
-you distribute copies of the software, or if you modify it: responsibilities to
-respect the freedom of others.
-
-For example, if you distribute copies of such a program, whether gratis or for a fee,
-you must pass on to the recipients the same freedoms that you received. You must make
-sure that they, too, receive or can get the source code. And you must show them these
-terms so they know their rights.
-
-Developers that use the GNU GPL protect your rights with two steps: **(1)** assert
-copyright on the software, and **(2)** offer you this License giving you legal permission
-to copy, distribute and/or modify it.
-
-For the developers' and authors' protection, the GPL clearly explains that there is
-no warranty for this free software. For both users' and authors' sake, the GPL
-requires that modified versions be marked as changed, so that their problems will not
-be attributed erroneously to authors of previous versions.
-
-Some devices are designed to deny users access to install or run modified versions of
-the software inside them, although the manufacturer can do so. This is fundamentally
-incompatible with the aim of protecting users' freedom to change the software. The
-systematic pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable. Therefore, we have designed
-this version of the GPL to prohibit the practice for those products. If such problems
-arise substantially in other domains, we stand ready to extend this provision to
-those domains in future versions of the GPL, as needed to protect the freedom of
-users.
-
-Finally, every program is threatened constantly by software patents. States should
-not allow patents to restrict development and use of software on general-purpose
-computers, but in those that do, we wish to avoid the special danger that patents
-applied to a free program could make it effectively proprietary. To prevent this, the
-GPL assures that patents cannot be used to render the program non-free.
-
-The precise terms and conditions for copying, distribution and modification follow.
+The GNU General Public License is a free, copyleft license for software and
+other kinds of works.
+
+The licenses for most software and other practical works are designed to take
+away your freedom to share and change the works. By contrast, the GNU General
+Public License is intended to guarantee your freedom to share and change all
+versions of a program--to make sure it remains free software for all its users.
+We, the Free Software Foundation, use the GNU General Public License for most of
+our software; it applies also to any other work released this way by its
+authors. You can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our
+General Public Licenses are designed to make sure that you have the freedom to
+distribute copies of free software (and charge for them if you wish), that you
+receive source code or can get it if you want it, that you can change the
+software or use pieces of it in new free programs, and that you know you can do
+these things.
+
+To protect your rights, we need to prevent others from denying you these rights
+or asking you to surrender the rights. Therefore, you have certain
+responsibilities if you distribute copies of the software, or if you modify it:
+responsibilities to respect the freedom of others.
+
+For example, if you distribute copies of such a program, whether gratis or for a
+fee, you must pass on to the recipients the same freedoms that you received. You
+must make sure that they, too, receive or can get the source code. And you must
+show them these terms so they know their rights.
+
+Developers that use the GNU GPL protect your rights with two steps: **(1)**
+assert copyright on the software, and **(2)** offer you this License giving you
+legal permission to copy, distribute and/or modify it.
+
+For the developers' and authors' protection, the GPL clearly explains that there
+is no warranty for this free software. For both users' and authors' sake, the
+GPL requires that modified versions be marked as changed, so that their problems
+will not be attributed erroneously to authors of previous versions.
+
+Some devices are designed to deny users access to install or run modified
+versions of the software inside them, although the manufacturer can do so. This
+is fundamentally incompatible with the aim of protecting users' freedom to
+change the software. The systematic pattern of such abuse occurs in the area of
+products for individuals to use, which is precisely where it is most
+unacceptable. Therefore, we have designed this version of the GPL to prohibit
+the practice for those products. If such problems arise substantially in other
+domains, we stand ready to extend this provision to those domains in future
+versions of the GPL, as needed to protect the freedom of users.
+
+Finally, every program is threatened constantly by software patents. States
+should not allow patents to restrict development and use of software on
+general-purpose computers, but in those that do, we wish to avoid the special
+danger that patents applied to a free program could make it effectively
+proprietary. To prevent this, the GPL assures that patents cannot be used to
+render the program non-free.
+
+The precise terms and conditions for copying, distribution and modification
+follow.
## TERMS AND CONDITIONS
@@ -70,70 +72,70 @@ The precise terms and conditions for copying, distribution and modification foll
“This License” refers to version 3 of the GNU General Public License.
-“Copyright” also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
+“Copyright” also means copyright-like laws that apply to other kinds of works,
+such as semiconductor masks.
-“The Program” refers to any copyrightable work licensed under this
-License. Each licensee is addressed as “you”. “Licensees” and
-“recipients” may be individuals or organizations.
+“The Program” refers to any copyrightable work licensed under this License. Each
+licensee is addressed as “you”. “Licensees” and “recipients” may be individuals
+or organizations.
-To “modify” a work means to copy from or adapt all or part of the work in
-a fashion requiring copyright permission, other than the making of an exact copy. The
-resulting work is called a “modified version” of the earlier work or a
-work “based on” the earlier work.
+To “modify” a work means to copy from or adapt all or part of the work in a
+fashion requiring copyright permission, other than the making of an exact copy.
+The resulting work is called a “modified version” of the earlier work or a work
+“based on” the earlier work.
-A “covered work” means either the unmodified Program or a work based on
-the Program.
+A “covered work” means either the unmodified Program or a work based on the
+Program.
-To “propagate” a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for infringement under
-applicable copyright law, except executing it on a computer or modifying a private
-copy. Propagation includes copying, distribution (with or without modification),
+To “propagate” a work means to do anything with it that, without permission,
+would make you directly or secondarily liable for infringement under applicable
+copyright law, except executing it on a computer or modifying a private copy.
+Propagation includes copying, distribution (with or without modification),
making available to the public, and in some countries other activities as well.
-To “convey” a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user through a computer
-network, with no transfer of a copy, is not conveying.
+To “convey” a work means any kind of propagation that enables other parties to
+make or receive copies. Mere interaction with a user through a computer network,
+with no transfer of a copy, is not conveying.
-An interactive user interface displays “Appropriate Legal Notices” to the
-extent that it includes a convenient and prominently visible feature that **(1)**
-displays an appropriate copyright notice, and **(2)** tells the user that there is no
-warranty for the work (except to the extent that warranties are provided), that
-licensees may convey the work under this License, and how to view a copy of this
-License. If the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
+An interactive user interface displays “Appropriate Legal Notices” to the extent
+that it includes a convenient and prominently visible feature that **(1)**
+displays an appropriate copyright notice, and **(2)** tells the user that there
+is no warranty for the work (except to the extent that warranties are provided),
+that licensees may convey the work under this License, and how to view a copy of
+this License. If the interface presents a list of user commands or options, such
+as a menu, a prominent item in the list meets this criterion.
### 1. Source Code
-The “source code” for a work means the preferred form of the work for
-making modifications to it. “Object code” means any non-source form of a
-work.
-
-A “Standard Interface” means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of interfaces
-specified for a particular programming language, one that is widely used among
-developers working in that language.
-
-The “System Libraries” of an executable work include anything, other than
-the work as a whole, that **(a)** is included in the normal form of packaging a Major
-Component, but which is not part of that Major Component, and **(b)** serves only to
-enable use of the work with that Major Component, or to implement a Standard
-Interface for which an implementation is available to the public in source code form.
-A “Major Component”, in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system (if any) on which
-the executable work runs, or a compiler used to produce the work, or an object code
-interpreter used to run it.
-
-The “Corresponding Source” for a work in object code form means all the
-source code needed to generate, install, and (for an executable work) run the object
-code and to modify the work, including scripts to control those activities. However,
-it does not include the work's System Libraries, or general-purpose tools or
-generally available free programs which are used unmodified in performing those
-activities but which are not part of the work. For example, Corresponding Source
-includes interface definition files associated with source files for the work, and
-the source code for shared libraries and dynamically linked subprograms that the work
-is specifically designed to require, such as by intimate data communication or
-control flow between those subprograms and other parts of the work.
+The “source code” for a work means the preferred form of the work for making
+modifications to it. “Object code” means any non-source form of a work.
+
+A “Standard Interface” means an interface that either is an official standard
+defined by a recognized standards body, or, in the case of interfaces specified
+for a particular programming language, one that is widely used among developers
+working in that language.
+
+The “System Libraries” of an executable work include anything, other than the
+work as a whole, that **(a)** is included in the normal form of packaging a
+Major Component, but which is not part of that Major Component, and **(b)**
+serves only to enable use of the work with that Major Component, or to implement
+a Standard Interface for which an implementation is available to the public in
+source code form. A “Major Component”, in this context, means a major essential
+component (kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to produce the
+work, or an object code interpreter used to run it.
+
+The “Corresponding Source” for a work in object code form means all the source
+code needed to generate, install, and (for an executable work) run the object
+code and to modify the work, including scripts to control those activities.
+However, it does not include the work's System Libraries, or general-purpose
+tools or generally available free programs which are used unmodified in
+performing those activities but which are not part of the work. For example,
+Corresponding Source includes interface definition files associated with source
+files for the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require, such as by
+intimate data communication or control flow between those subprograms and other
+parts of the work.
The Corresponding Source need not include anything that users can regenerate
automatically from other parts of the Corresponding Source.
@@ -142,328 +144,341 @@ The Corresponding Source for a work in source code form is that same work.
### 2. Basic Permissions
-All rights granted under this License are granted for the term of copyright on the
-Program, and are irrevocable provided the stated conditions are met. This License
-explicitly affirms your unlimited permission to run the unmodified Program. The
-output from running a covered work is covered by this License only if the output,
-given its content, constitutes a covered work. This License acknowledges your rights
-of fair use or other equivalent, as provided by copyright law.
+All rights granted under this License are granted for the term of copyright on
+the Program, and are irrevocable provided the stated conditions are met. This
+License explicitly affirms your unlimited permission to run the unmodified
+Program. The output from running a covered work is covered by this License only
+if the output, given its content, constitutes a covered work. This License
+acknowledges your rights of fair use or other equivalent, as provided by
+copyright law.
You may make, run and propagate covered works that you do not convey, without
-conditions so long as your license otherwise remains in force. You may convey covered
-works to others for the sole purpose of having them make modifications exclusively
-for you, or provide you with facilities for running those works, provided that you
-comply with the terms of this License in conveying all material for which you do not
-control copyright. Those thus making or running the covered works for you must do so
-exclusively on your behalf, under your direction and control, on terms that prohibit
-them from making any copies of your copyrighted material outside their relationship
-with you.
+conditions so long as your license otherwise remains in force. You may convey
+covered works to others for the sole purpose of having them make modifications
+exclusively for you, or provide you with facilities for running those works,
+provided that you comply with the terms of this License in conveying all
+material for which you do not control copyright. Those thus making or running
+the covered works for you must do so exclusively on your behalf, under your
+direction and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the conditions
stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
### 3. Protecting Users' Legal Rights From Anti-Circumvention Law
-No covered work shall be deemed part of an effective technological measure under any
-applicable law fulfilling obligations under article 11 of the WIPO copyright treaty
-adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention
-of such measures.
+No covered work shall be deemed part of an effective technological measure under
+any applicable law fulfilling obligations under article 11 of the WIPO copyright
+treaty adopted on 20 December 1996, or similar laws prohibiting or restricting
+circumvention of such measures.
-When you convey a covered work, you waive any legal power to forbid circumvention of
-technological measures to the extent such circumvention is effected by exercising
-rights under this License with respect to the covered work, and you disclaim any
-intention to limit operation or modification of the work as a means of enforcing,
-against the work's users, your or third parties' legal rights to forbid circumvention
-of technological measures.
+When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention is
+effected by exercising rights under this License with respect to the covered
+work, and you disclaim any intention to limit operation or modification of the
+work as a means of enforcing, against the work's users, your or third parties'
+legal rights to forbid circumvention of technological measures.
### 4. Conveying Verbatim Copies
-You may convey verbatim copies of the Program's source code as you receive it, in any
-medium, provided that you conspicuously and appropriately publish on each copy an
-appropriate copyright notice; keep intact all notices stating that this License and
-any non-permissive terms added in accord with section 7 apply to the code; keep
-intact all notices of the absence of any warranty; and give all recipients a copy of
-this License along with the Program.
+You may convey verbatim copies of the Program's source code as you receive it,
+in any medium, provided that you conspicuously and appropriately publish on each
+copy an appropriate copyright notice; keep intact all notices stating that this
+License and any non-permissive terms added in accord with section 7 apply to the
+code; keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
-You may charge any price or no price for each copy that you convey, and you may offer
-support or warranty protection for a fee.
+You may charge any price or no price for each copy that you convey, and you may
+offer support or warranty protection for a fee.
### 5. Conveying Modified Source Versions
-You may convey a work based on the Program, or the modifications to produce it from
-the Program, in the form of source code under the terms of section 4, provided that
-you also meet all of these conditions:
-
-* **a)** The work must carry prominent notices stating that you modified it, and giving a
-relevant date.
-* **b)** The work must carry prominent notices stating that it is released under this
-License and any conditions added under section 7. This requirement modifies the
-requirement in section 4 to “keep intact all notices”.
-* **c)** You must license the entire work, as a whole, under this License to anyone who
-comes into possession of a copy. This License will therefore apply, along with any
-applicable section 7 additional terms, to the whole of the work, and all its parts,
-regardless of how they are packaged. This License gives no permission to license the
-work in any other way, but it does not invalidate such permission if you have
-separately received it.
-* **d)** If the work has interactive user interfaces, each must display Appropriate Legal
-Notices; however, if the Program has interactive interfaces that do not display
-Appropriate Legal Notices, your work need not make them do so.
-
-A compilation of a covered work with other separate and independent works, which are
-not by their nature extensions of the covered work, and which are not combined with
-it such as to form a larger program, in or on a volume of a storage or distribution
-medium, is called an “aggregate” if the compilation and its resulting
-copyright are not used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work in an aggregate
-does not cause this License to apply to the other parts of the aggregate.
+You may convey a work based on the Program, or the modifications to produce it
+from the Program, in the form of source code under the terms of section 4,
+provided that you also meet all of these conditions:
+
+- **a)** The work must carry prominent notices stating that you modified it, and
+ giving a relevant date.
+- **b)** The work must carry prominent notices stating that it is released under
+ this License and any conditions added under section 7. This requirement
+ modifies the requirement in section 4 to “keep intact all notices”.
+- **c)** You must license the entire work, as a whole, under this License to
+ anyone who comes into possession of a copy. This License will therefore apply,
+ along with any applicable section 7 additional terms, to the whole of the
+ work, and all its parts, regardless of how they are packaged. This License
+ gives no permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+- **d)** If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive interfaces
+ that do not display Appropriate Legal Notices, your work need not make them do
+ so.
+
+A compilation of a covered work with other separate and independent works, which
+are not by their nature extensions of the covered work, and which are not
+combined with it such as to form a larger program, in or on a volume of a
+storage or distribution medium, is called an “aggregate” if the compilation and
+its resulting copyright are not used to limit the access or legal rights of the
+compilation's users beyond what the individual works permit. Inclusion of a
+covered work in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
### 6. Conveying Non-Source Forms
-You may convey a covered work in object code form under the terms of sections 4 and
-5, provided that you also convey the machine-readable Corresponding Source under the
-terms of this License, in one of these ways:
-
-* **a)** Convey the object code in, or embodied in, a physical product (including a
-physical distribution medium), accompanied by the Corresponding Source fixed on a
-durable physical medium customarily used for software interchange.
-* **b)** Convey the object code in, or embodied in, a physical product (including a
-physical distribution medium), accompanied by a written offer, valid for at least
-three years and valid for as long as you offer spare parts or customer support for
-that product model, to give anyone who possesses the object code either **(1)** a copy of
-the Corresponding Source for all the software in the product that is covered by this
-License, on a durable physical medium customarily used for software interchange, for
-a price no more than your reasonable cost of physically performing this conveying of
-source, or **(2)** access to copy the Corresponding Source from a network server at no
-charge.
-* **c)** Convey individual copies of the object code with a copy of the written offer to
-provide the Corresponding Source. This alternative is allowed only occasionally and
-noncommercially, and only if you received the object code with such an offer, in
-accord with subsection 6b.
-* **d)** Convey the object code by offering access from a designated place (gratis or for
-a charge), and offer equivalent access to the Corresponding Source in the same way
-through the same place at no further charge. You need not require recipients to copy
-the Corresponding Source along with the object code. If the place to copy the object
-code is a network server, the Corresponding Source may be on a different server
-(operated by you or a third party) that supports equivalent copying facilities,
-provided you maintain clear directions next to the object code saying where to find
-the Corresponding Source. Regardless of what server hosts the Corresponding Source,
-you remain obligated to ensure that it is available for as long as needed to satisfy
-these requirements.
-* **e)** Convey the object code using peer-to-peer transmission, provided you inform
-other peers where the object code and Corresponding Source of the work are being
-offered to the general public at no charge under subsection 6d.
+You may convey a covered work in object code form under the terms of sections 4
+and 5, provided that you also convey the machine-readable Corresponding Source
+under the terms of this License, in one of these ways:
+
+- **a)** Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the Corresponding
+ Source fixed on a durable physical medium customarily used for software
+ interchange.
+- **b)** Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a written offer,
+ valid for at least three years and valid for as long as you offer spare parts
+ or customer support for that product model, to give anyone who possesses the
+ object code either **(1)** a copy of the Corresponding Source for all the
+ software in the product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no more than
+ your reasonable cost of physically performing this conveying of source, or
+ **(2)** access to copy the Corresponding Source from a network server at no
+ charge.
+- **c)** Convey individual copies of the object code with a copy of the written
+ offer to provide the Corresponding Source. This alternative is allowed only
+ occasionally and noncommercially, and only if you received the object code
+ with such an offer, in accord with subsection 6b.
+- **d)** Convey the object code by offering access from a designated place
+ (gratis or for a charge), and offer equivalent access to the Corresponding
+ Source in the same way through the same place at no further charge. You need
+ not require recipients to copy the Corresponding Source along with the object
+ code. If the place to copy the object code is a network server, the
+ Corresponding Source may be on a different server (operated by you or a third
+ party) that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the Corresponding
+ Source, you remain obligated to ensure that it is available for as long as
+ needed to satisfy these requirements.
+- **e)** Convey the object code using peer-to-peer transmission, provided you
+ inform other peers where the object code and Corresponding Source of the work
+ are being offered to the general public at no charge under subsection 6d.
A separable portion of the object code, whose source code is excluded from the
Corresponding Source as a System Library, need not be included in conveying the
object code work.
-A “User Product” is either **(1)** a “consumer product”, which
-means any tangible personal property which is normally used for personal, family, or
-household purposes, or **(2)** anything designed or sold for incorporation into a
-dwelling. In determining whether a product is a consumer product, doubtful cases
-shall be resolved in favor of coverage. For a particular product received by a
-particular user, “normally used” refers to a typical or common use of
-that class of product, regardless of the status of the particular user or of the way
-in which the particular user actually uses, or expects or is expected to use, the
-product. A product is a consumer product regardless of whether the product has
-substantial commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-“Installation Information” for a User Product means any methods,
-procedures, authorization keys, or other information required to install and execute
-modified versions of a covered work in that User Product from a modified version of
-its Corresponding Source. The information must suffice to ensure that the continued
-functioning of the modified object code is in no case prevented or interfered with
-solely because modification has been made.
-
-If you convey an object code work under this section in, or with, or specifically for
-use in, a User Product, and the conveying occurs as part of a transaction in which
-the right of possession and use of the User Product is transferred to the recipient
-in perpetuity or for a fixed term (regardless of how the transaction is
-characterized), the Corresponding Source conveyed under this section must be
-accompanied by the Installation Information. But this requirement does not apply if
-neither you nor any third party retains the ability to install modified object code
-on the User Product (for example, the work has been installed in ROM).
-
-The requirement to provide Installation Information does not include a requirement to
-continue to provide support service, warranty, or updates for a work that has been
-modified or installed by the recipient, or for the User Product in which it has been
-modified or installed. Access to a network may be denied when the modification itself
-materially and adversely affects the operation of the network or violates the rules
-and protocols for communication across the network.
-
-Corresponding Source conveyed, and Installation Information provided, in accord with
-this section must be in a format that is publicly documented (and with an
+A “User Product” is either **(1)** a “consumer product”, which means any
+tangible personal property which is normally used for personal, family, or
+household purposes, or **(2)** anything designed or sold for incorporation into
+a dwelling. In determining whether a product is a consumer product, doubtful
+cases shall be resolved in favor of coverage. For a particular product received
+by a particular user, “normally used” refers to a typical or common use of that
+class of product, regardless of the status of the particular user or of the way
+in which the particular user actually uses, or expects or is expected to use,
+the product. A product is a consumer product regardless of whether the product
+has substantial commercial, industrial or non-consumer uses, unless such uses
+represent the only significant mode of use of the product.
+
+“Installation Information” for a User Product means any methods, procedures,
+authorization keys, or other information required to install and execute
+modified versions of a covered work in that User Product from a modified version
+of its Corresponding Source. The information must suffice to ensure that the
+continued functioning of the modified object code is in no case prevented or
+interfered with solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as part of a
+transaction in which the right of possession and use of the User Product is
+transferred to the recipient in perpetuity or for a fixed term (regardless of
+how the transaction is characterized), the Corresponding Source conveyed under
+this section must be accompanied by the Installation Information. But this
+requirement does not apply if neither you nor any third party retains the
+ability to install modified object code on the User Product (for example, the
+work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates for a
+work that has been modified or installed by the recipient, or for the User
+Product in which it has been modified or installed. Access to a network may be
+denied when the modification itself materially and adversely affects the
+operation of the network or violates the rules and protocols for communication
+across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord
+with this section must be in a format that is publicly documented (and with an
implementation available to the public in source code form), and must require no
special password or key for unpacking, reading or copying.
### 7. Additional Terms
-“Additional permissions” are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions. Additional
-permissions that are applicable to the entire Program shall be treated as though they
-were included in this License, to the extent that they are valid under applicable
-law. If additional permissions apply only to part of the Program, that part may be
-used separately under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
+“Additional permissions” are terms that supplement the terms of this License by
+making exceptions from one or more of its conditions. Additional permissions
+that are applicable to the entire Program shall be treated as though they were
+included in this License, to the extent that they are valid under applicable
+law. If additional permissions apply only to part of the Program, that part may
+be used separately under those permissions, but the entire Program remains
+governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any
additional permissions from that copy, or from any part of it. (Additional
-permissions may be written to require their own removal in certain cases when you
-modify the work.) You may place additional permissions on material, added by you to a
-covered work, for which you have or can give appropriate copyright permission.
+permissions may be written to require their own removal in certain cases when
+you modify the work.) You may place additional permissions on material, added by
+you to a covered work, for which you have or can give appropriate copyright
+permission.
Notwithstanding any other provision of this License, for material you add to a
covered work, you may (if authorized by the copyright holders of that material)
supplement the terms of this License with terms:
-* **a)** Disclaiming warranty or limiting liability differently from the terms of
-sections 15 and 16 of this License; or
-* **b)** Requiring preservation of specified reasonable legal notices or author
-attributions in that material or in the Appropriate Legal Notices displayed by works
-containing it; or
-* **c)** Prohibiting misrepresentation of the origin of that material, or requiring that
-modified versions of such material be marked in reasonable ways as different from the
-original version; or
-* **d)** Limiting the use for publicity purposes of names of licensors or authors of the
-material; or
-* **e)** Declining to grant rights under trademark law for use of some trade names,
-trademarks, or service marks; or
-* **f)** Requiring indemnification of licensors and authors of that material by anyone
-who conveys the material (or modified versions of it) with contractual assumptions of
-liability to the recipient, for any liability that these contractual assumptions
-directly impose on those licensors and authors.
-
-All other non-permissive additional terms are considered “further
-restrictions” within the meaning of section 10. If the Program as you received
-it, or any part of it, contains a notice stating that it is governed by this License
-along with a term that is a further restriction, you may remove that term. If a
-license document contains a further restriction but permits relicensing or conveying
-under this License, you may add to a covered work material governed by the terms of
-that license document, provided that the further restriction does not survive such
-relicensing or conveying.
-
-If you add terms to a covered work in accord with this section, you must place, in
-the relevant source files, a statement of the additional terms that apply to those
-files, or a notice indicating where to find the applicable terms.
+- **a)** Disclaiming warranty or limiting liability differently from the terms
+ of sections 15 and 16 of this License; or
+- **b)** Requiring preservation of specified reasonable legal notices or author
+ attributions in that material or in the Appropriate Legal Notices displayed by
+ works containing it; or
+- **c)** Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in reasonable ways
+ as different from the original version; or
+- **d)** Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+- **e)** Declining to grant rights under trademark law for use of some trade
+ names, trademarks, or service marks; or
+- **f)** Requiring indemnification of licensors and authors of that material by
+ anyone who conveys the material (or modified versions of it) with contractual
+ assumptions of liability to the recipient, for any liability that these
+ contractual assumptions directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered “further restrictions”
+within the meaning of section 10. If the Program as you received it, or any part
+of it, contains a notice stating that it is governed by this License along with
+a term that is a further restriction, you may remove that term. If a license
+document contains a further restriction but permits relicensing or conveying
+under this License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does not survive
+such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place,
+in the relevant source files, a statement of the additional terms that apply to
+those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a
-separately written license, or stated as exceptions; the above requirements apply
-either way.
+separately written license, or stated as exceptions; the above requirements
+apply either way.
### 8. Termination
-You may not propagate or modify a covered work except as expressly provided under
-this License. Any attempt otherwise to propagate or modify it is void, and will
-automatically terminate your rights under this License (including any patent licenses
-granted under the third paragraph of section 11).
+You may not propagate or modify a covered work except as expressly provided
+under this License. Any attempt otherwise to propagate or modify it is void, and
+will automatically terminate your rights under this License (including any
+patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a
-particular copyright holder is reinstated **(a)** provisionally, unless and until the
-copyright holder explicitly and finally terminates your license, and **(b)** permanently,
-if the copyright holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
+particular copyright holder is reinstated **(a)** provisionally, unless and
+until the copyright holder explicitly and finally terminates your license, and
+**(b)** permanently, if the copyright holder fails to notify you of the
+violation by some reasonable means prior to 60 days after the cessation.
-Moreover, your license from a particular copyright holder is reinstated permanently
-if the copyright holder notifies you of the violation by some reasonable means, this
-is the first time you have received notice of violation of this License (for any
-work) from that copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
+Moreover, your license from a particular copyright holder is reinstated
+permanently if the copyright holder notifies you of the violation by some
+reasonable means, this is the first time you have received notice of violation
+of this License (for any work) from that copyright holder, and you cure the
+violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of
parties who have received copies or rights from you under this License. If your
-rights have been terminated and not permanently reinstated, you do not qualify to
-receive new licenses for the same material under section 10.
+rights have been terminated and not permanently reinstated, you do not qualify
+to receive new licenses for the same material under section 10.
### 9. Acceptance Not Required for Having Copies
-You are not required to accept this License in order to receive or run a copy of the
-Program. Ancillary propagation of a covered work occurring solely as a consequence of
-using peer-to-peer transmission to receive a copy likewise does not require
-acceptance. However, nothing other than this License grants you permission to
-propagate or modify any covered work. These actions infringe copyright if you do not
-accept this License. Therefore, by modifying or propagating a covered work, you
-indicate your acceptance of this License to do so.
+You are not required to accept this License in order to receive or run a copy of
+the Program. Ancillary propagation of a covered work occurring solely as a
+consequence of using peer-to-peer transmission to receive a copy likewise does
+not require acceptance. However, nothing other than this License grants you
+permission to propagate or modify any covered work. These actions infringe
+copyright if you do not accept this License. Therefore, by modifying or
+propagating a covered work, you indicate your acceptance of this License to do
+so.
### 10. Automatic Licensing of Downstream Recipients
-Each time you convey a covered work, the recipient automatically receives a license
-from the original licensors, to run, modify and propagate that work, subject to this
-License. You are not responsible for enforcing compliance by third parties with this
-License.
+Each time you convey a covered work, the recipient automatically receives a
+license from the original licensors, to run, modify and propagate that work,
+subject to this License. You are not responsible for enforcing compliance by
+third parties with this License.
An “entity transaction” is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an organization, or
-merging organizations. If propagation of a covered work results from an entity
-transaction, each party to that transaction who receives a copy of the work also
-receives whatever licenses to the work the party's predecessor in interest had or
-could give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if the predecessor
-has it or can get it with reasonable efforts.
-
-You may not impose any further restrictions on the exercise of the rights granted or
-affirmed under this License. For example, you may not impose a license fee, royalty,
-or other charge for exercise of rights granted under this License, and you may not
-initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging
-that any patent claim is infringed by making, using, selling, offering for sale, or
-importing the Program or any portion of it.
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered work results
+from an entity transaction, each party to that transaction who receives a copy
+of the work also receives whatever licenses to the work the party's predecessor
+in interest had or could give under the previous paragraph, plus a right to
+possession of the Corresponding Source of the work from the predecessor in
+interest, if the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights
+granted or affirmed under this License. For example, you may not impose a
+license fee, royalty, or other charge for exercise of rights granted under this
+License, and you may not initiate litigation (including a cross-claim or
+counterclaim in a lawsuit) alleging that any patent claim is infringed by
+making, using, selling, offering for sale, or importing the Program or any
+portion of it.
### 11. Patents
-A “contributor” is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The work thus
-licensed is called the contributor's “contributor version”.
+A “contributor” is a copyright holder who authorizes use under this License of
+the Program or a work on which the Program is based. The work thus licensed is
+called the contributor's “contributor version”.
A contributor's “essential patent claims” are all patent claims owned or
-controlled by the contributor, whether already acquired or hereafter acquired, that
-would be infringed by some manner, permitted by this License, of making, using, or
-selling its contributor version, but do not include claims that would be infringed
-only as a consequence of further modification of the contributor version. For
-purposes of this definition, “control” includes the right to grant patent
-sublicenses in a manner consistent with the requirements of this License.
-
-Each contributor grants you a non-exclusive, worldwide, royalty-free patent license
-under the contributor's essential patent claims, to make, use, sell, offer for sale,
-import and otherwise run, modify and propagate the contents of its contributor
-version.
-
-In the following three paragraphs, a “patent license” is any express
-agreement or commitment, however denominated, not to enforce a patent (such as an
-express permission to practice a patent or covenant not to sue for patent
-infringement). To “grant” such a patent license to a party means to make
-such an agreement or commitment not to enforce a patent against the party.
+controlled by the contributor, whether already acquired or hereafter acquired,
+that would be infringed by some manner, permitted by this License, of making,
+using, or selling its contributor version, but do not include claims that would
+be infringed only as a consequence of further modification of the contributor
+version. For purposes of this definition, “control” includes the right to grant
+patent sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent
+license under the contributor's essential patent claims, to make, use, sell,
+offer for sale, import and otherwise run, modify and propagate the contents of
+its contributor version.
+
+In the following three paragraphs, a “patent license” is any express agreement
+or commitment, however denominated, not to enforce a patent (such as an express
+permission to practice a patent or covenant not to sue for patent infringement).
+To “grant” such a patent license to a party means to make such an agreement or
+commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license, and the
-Corresponding Source of the work is not available for anyone to copy, free of charge
-and under the terms of this License, through a publicly available network server or
-other readily accessible means, then you must either **(1)** cause the Corresponding
-Source to be so available, or **(2)** arrange to deprive yourself of the benefit of the
-patent license for this particular work, or **(3)** arrange, in a manner consistent with
-the requirements of this License, to extend the patent license to downstream
-recipients. “Knowingly relying” means you have actual knowledge that, but
-for the patent license, your conveying the covered work in a country, or your
-recipient's use of the covered work in a country, would infringe one or more
-identifiable patents in that country that you have reason to believe are valid.
+Corresponding Source of the work is not available for anyone to copy, free of
+charge and under the terms of this License, through a publicly available network
+server or other readily accessible means, then you must either **(1)** cause the
+Corresponding Source to be so available, or **(2)** arrange to deprive yourself
+of the benefit of the patent license for this particular work, or **(3)**
+arrange, in a manner consistent with the requirements of this License, to extend
+the patent license to downstream recipients. “Knowingly relying” means you have
+actual knowledge that, but for the patent license, your conveying the covered
+work in a country, or your recipient's use of the covered work in a country,
+would infringe one or more identifiable patents in that country that you have
+reason to believe are valid.
If, pursuant to or in connection with a single transaction or arrangement, you
-convey, or propagate by procuring conveyance of, a covered work, and grant a patent
-license to some of the parties receiving the covered work authorizing them to use,
-propagate, modify or convey a specific copy of the covered work, then the patent
-license you grant is automatically extended to all recipients of the covered work and
-works based on it.
-
-A patent license is “discriminatory” if it does not include within the
-scope of its coverage, prohibits the exercise of, or is conditioned on the
-non-exercise of one or more of the rights that are specifically granted under this
-License. You may not convey a covered work if you are a party to an arrangement with
-a third party that is in the business of distributing software, under which you make
-payment to the third party based on the extent of your activity of conveying the
-work, and under which the third party grants, to any of the parties who would receive
-the covered work from you, a discriminatory patent license **(a)** in connection with
-copies of the covered work conveyed by you (or copies made from those copies), or **(b)**
-primarily for and in connection with specific products or compilations that contain
-the covered work, unless you entered into that arrangement, or that patent license
-was granted, prior to 28 March 2007.
+convey, or propagate by procuring conveyance of, a covered work, and grant a
+patent license to some of the parties receiving the covered work authorizing
+them to use, propagate, modify or convey a specific copy of the covered work,
+then the patent license you grant is automatically extended to all recipients of
+the covered work and works based on it.
+
+A patent license is “discriminatory” if it does not include within the scope of
+its coverage, prohibits the exercise of, or is conditioned on the non-exercise
+of one or more of the rights that are specifically granted under this License.
+You may not convey a covered work if you are a party to an arrangement with a
+third party that is in the business of distributing software, under which you
+make payment to the third party based on the extent of your activity of
+conveying the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory patent
+license **(a)** in connection with copies of the covered work conveyed by you
+(or copies made from those copies), or **(b)** primarily for and in connection
+with specific products or compilations that contain the covered work, unless you
+entered into that arrangement, or that patent license was granted, prior to 28
+March 2007.
Nothing in this License shall be construed as excluding or limiting any implied
license or other defenses to infringement that may otherwise be available to you
@@ -471,51 +486,55 @@ under applicable patent law.
### 12. No Surrender of Others' Freedom
-If conditions are imposed on you (whether by court order, agreement or otherwise)
-that contradict the conditions of this License, they do not excuse you from the
-conditions of this License. If you cannot convey a covered work so as to satisfy
-simultaneously your obligations under this License and any other pertinent
-obligations, then as a consequence you may not convey it at all. For example, if you
-agree to terms that obligate you to collect a royalty for further conveying from
-those to whom you convey the Program, the only way you could satisfy both those terms
-and this License would be to refrain entirely from conveying the Program.
+If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not excuse
+you from the conditions of this License. If you cannot convey a covered work so
+as to satisfy simultaneously your obligations under this License and any other
+pertinent obligations, then as a consequence you may not convey it at all. For
+example, if you agree to terms that obligate you to collect a royalty for
+further conveying from those to whom you convey the Program, the only way you
+could satisfy both those terms and this License would be to refrain entirely
+from conveying the Program.
### 13. Use with the GNU Affero General Public License
-Notwithstanding any other provision of this License, you have permission to link or
-combine any covered work with a work licensed under version 3 of the GNU Affero
-General Public License into a single combined work, and to convey the resulting work.
-The terms of this License will continue to apply to the part which is the covered
-work, but the special requirements of the GNU Affero General Public License, section
-13, concerning interaction through a network will apply to the combination as such.
+Notwithstanding any other provision of this License, you have permission to link
+or combine any covered work with a work licensed under version 3 of the GNU
+Affero General Public License into a single combined work, and to convey the
+resulting work. The terms of this License will continue to apply to the part
+which is the covered work, but the special requirements of the GNU Affero
+General Public License, section 13, concerning interaction through a network
+will apply to the combination as such.
### 14. Revised Versions of this License
The Free Software Foundation may publish revised and/or new versions of the GNU
-General Public License from time to time. Such new versions will be similar in spirit
-to the present version, but may differ in detail to address new problems or concerns.
+General Public License from time to time. Such new versions will be similar in
+spirit to the present version, but may differ in detail to address new problems
+or concerns.
-Each version is given a distinguishing version number. If the Program specifies that
-a certain numbered version of the GNU General Public License “or any later
+Each version is given a distinguishing version number. If the Program specifies
+that a certain numbered version of the GNU General Public License “or any later
version” applies to it, you have the option of following the terms and
-conditions either of that numbered version or of any later version published by the
-Free Software Foundation. If the Program does not specify a version number of the GNU
-General Public License, you may choose any version ever published by the Free
-Software Foundation.
-
-If the Program specifies that a proxy can decide which future versions of the GNU
-General Public License can be used, that proxy's public statement of acceptance of a
-version permanently authorizes you to choose that version for the Program.
+conditions either of that numbered version or of any later version published by
+the Free Software Foundation. If the Program does not specify a version number
+of the GNU General Public License, you may choose any version ever published by
+the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the
+GNU General Public License can be used, that proxy's public statement of
+acceptance of a version permanently authorizes you to choose that version for
+the Program.
-Later license versions may give you additional or different permissions. However, no
-additional obligations are imposed on any author or copyright holder as a result of
-your choosing to follow a later version.
+Later license versions may give you additional or different permissions.
+However, no additional obligations are imposed on any author or copyright holder
+as a result of your choosing to follow a later version.
### 15. Disclaimer of Warranty
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER
+PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
@@ -526,32 +545,32 @@ DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS
PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
-WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
+THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
+INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE
+PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY
+HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
### 17. Interpretation of Sections 15 and 16
-If the disclaimer of warranty and limitation of liability provided above cannot be
-given local legal effect according to their terms, reviewing courts shall apply local
-law that most closely approximates an absolute waiver of all civil liability in
-connection with the Program, unless a warranty or assumption of liability accompanies
-a copy of the Program in return for a fee.
+If the disclaimer of warranty and limitation of liability provided above cannot
+be given local legal effect according to their terms, reviewing courts shall
+apply local law that most closely approximates an absolute waiver of all civil
+liability in connection with the Program, unless a warranty or assumption of
+liability accompanies a copy of the Program in return for a fee.
_END OF TERMS AND CONDITIONS_
## How to Apply These Terms to Your New Programs
-If you develop a new program, and you want it to be of the greatest possible use to
-the public, the best way to achieve this is to make it free software which everyone
-can redistribute and change under these terms.
+If you develop a new program, and you want it to be of the greatest possible use
+to the public, the best way to achieve this is to make it free software which
+everyone can redistribute and change under these terms.
-To do so, attach the following notices to the program. It is safest to attach them
-to the start of each source file to most effectively state the exclusion of warranty;
-and each file should have at least the “copyright” line and a pointer to
-where the full notice is found.
+To do so, attach the following notices to the program. It is safest to attach
+them to the start of each source file to most effectively state the exclusion of
+warranty; and each file should have at least the “copyright” line and a pointer
+to where the full notice is found.
Copyright (C)
@@ -571,26 +590,26 @@ where the full notice is found.
Also add information on how to contact you by electronic and paper mail.
-If the program does terminal interaction, make it output a short notice like this
-when it starts in an interactive mode:
+If the program does terminal interaction, make it output a short notice like
+this when it starts in an interactive mode:
Copyright (C)
This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type 'show c' for details.
-The hypothetical commands `show w` and `show c` should show the appropriate parts of
-the General Public License. Of course, your program's commands might be different;
-for a GUI interface, you would use an “about box”.
+The hypothetical commands `show w` and `show c` should show the appropriate
+parts of the General Public License. Of course, your program's commands might be
+different; for a GUI interface, you would use an “about box”.
-You should also get your employer (if you work as a programmer) or school, if any, to
-sign a “copyright disclaimer” for the program, if necessary. For more
+You should also get your employer (if you work as a programmer) or school, if
+any, to sign a “copyright disclaimer” for the program, if necessary. For more
information on this, and how to apply and follow the GNU GPL, see
<>.
The GNU General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may consider it
-more useful to permit linking proprietary applications with the library. If this is
-what you want to do, use the GNU Lesser General Public License instead of this
-License. But first, please read
+proprietary programs. If your program is a subroutine library, you may consider
+it more useful to permit linking proprietary applications with the library. If
+this is what you want to do, use the GNU Lesser General Public License instead
+of this License. But first, please read
<>.
diff --git a/PUBLISH.md b/PUBLISH.md
index 9c2994c11..513e924b1 100644
--- a/PUBLISH.md
+++ b/PUBLISH.md
@@ -10,4 +10,4 @@ cd ../sdk && npm publish --access public
cd ../create-leo-app & npm publish --access public
git tag vX.X.X
git push origin vX.X.X
-```
\ No newline at end of file
+```
diff --git a/README.md b/README.md
index 65b4fae60..cce53094c 100644
--- a/README.md
+++ b/README.md
@@ -4,11 +4,12 @@