From 3c5addd7d64b0d906af8a764d92ad56e4152ecfc Mon Sep 17 00:00:00 2001 From: benesjan Date: Thu, 28 Sep 2023 11:33:53 +0100 Subject: [PATCH] fixes --- docs/docs/dev_docs/tutorials/testing.md | 2 +- .../docs/dev_docs/tutorials/writing_dapp/contract_deployment.md | 2 +- .../dev_docs/tutorials/writing_dapp/contract_interaction.md | 2 +- docs/docs/dev_docs/wallets/creating_schnorr_accounts.md | 2 +- yarn-project/aztec-node/README.md | 2 +- yarn-project/end-to-end/src/fixtures/utils.ts | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/docs/dev_docs/tutorials/testing.md b/docs/docs/dev_docs/tutorials/testing.md index db094fafdb0..5a5780de271 100644 --- a/docs/docs/dev_docs/tutorials/testing.md +++ b/docs/docs/dev_docs/tutorials/testing.md @@ -137,7 +137,7 @@ Private state in the Aztec Network is represented via sets of [private notes](.. #include_code value-note-def yarn-project/aztec-nr/value-note/src/value_note.nr rust -We can query the Private eXecution Service (PXE) for all notes encrypted for a given user in a contract slot. For this example, we'll get all notes encrypted for the `owner` user that are stored on the token contract address and on the slot we calculated earlier. To calculate the actual balance, we extract the `value` of each note, which is the first element, and sum them up. +We can query the Private eXecution Environment (PXE) for all notes encrypted for a given user in a contract slot. For this example, we'll get all notes encrypted for the `owner` user that are stored on the token contract address and on the slot we calculated earlier. To calculate the actual balance, we extract the `value` of each note, which is the first element, and sum them up. #include_code private-storage /yarn-project/end-to-end/src/guides/dapp_testing.test.ts typescript diff --git a/docs/docs/dev_docs/tutorials/writing_dapp/contract_deployment.md b/docs/docs/dev_docs/tutorials/writing_dapp/contract_deployment.md index ad278e73a11..83ddeebce38 100644 --- a/docs/docs/dev_docs/tutorials/writing_dapp/contract_deployment.md +++ b/docs/docs/dev_docs/tutorials/writing_dapp/contract_deployment.md @@ -60,7 +60,7 @@ This should have created an artifact `contracts/token/target/Token.json` with th ## Deploy your contracts -Let's now write a script for deploying your contracts to the Sandbox. We'll create a Private eXecution Service (PXE) client, and then use the `ContractDeployer` class to deploy our contracts, and store the deployment address to a local JSON file. +Let's now write a script for deploying your contracts to the Sandbox. We'll create a Private eXecution Environment (PXE) client, and then use the `ContractDeployer` class to deploy our contracts, and store the deployment address to a local JSON file. Create a new file `src/deploy.mjs`: diff --git a/docs/docs/dev_docs/tutorials/writing_dapp/contract_interaction.md b/docs/docs/dev_docs/tutorials/writing_dapp/contract_interaction.md index 65a3f0ecce8..daed14e63fb 100644 --- a/docs/docs/dev_docs/tutorials/writing_dapp/contract_interaction.md +++ b/docs/docs/dev_docs/tutorials/writing_dapp/contract_interaction.md @@ -9,7 +9,7 @@ Let's start by showing our user's private balance for the token across their acc #include_code balance_of_private yarn-project/noir-contracts/src/contracts/token_contract/src/main.nr rust :::info -Note that this function will only return a valid response for accounts registered in the Private eXecution Service (PXE), since it requires access to the [user's private state](../../wallets/main.md#private-state). In other words, you cannot query the private balance of another user for the token contract. +Note that this function will only return a valid response for accounts registered in the Private eXecution Environment (PXE), since it requires access to the [user's private state](../../wallets/main.md#private-state). In other words, you cannot query the private balance of another user for the token contract. ::: To do this, let's first initialize a new `Contract` instance using `aztec.js` that represents our deployed token contracts. Create a new `src/contracts.mjs` file with the imports for our artifacts and other dependencies: diff --git a/docs/docs/dev_docs/wallets/creating_schnorr_accounts.md b/docs/docs/dev_docs/wallets/creating_schnorr_accounts.md index cc757849903..7b0a43c0a54 100644 --- a/docs/docs/dev_docs/wallets/creating_schnorr_accounts.md +++ b/docs/docs/dev_docs/wallets/creating_schnorr_accounts.md @@ -9,7 +9,7 @@ This section shows how to create schnorr account wallets on the Aztec Sandbox. An in-depth explaining about accounts on aztec can be found [here](../../concepts/foundation/accounts/main.md). But creating an account on the Sandbox does 2 things: 1. Deploys an account contract -- representing you -- allowing you to perform actions on the network (deploy contracts, call functions etc). -2. Adds your encryption keys to the Private eXecution Service (PXE) allowing it to decrypt and manage your private state. +2. Adds your encryption keys to the Private eXecution Environment (PXE) allowing it to decrypt and manage your private state. ## Pre-requisites diff --git a/yarn-project/aztec-node/README.md b/yarn-project/aztec-node/README.md index 3b2374b6eda..7ea0c8335ba 100644 --- a/yarn-project/aztec-node/README.md +++ b/yarn-project/aztec-node/README.md @@ -2,7 +2,7 @@ The Aztec Node implements a sequencer node in the network, and is currently meant to be used for local development and testing. The Node is the entrypoint for creating and starting a new Sequencer client with default components (a local P2P client, an in-memory merkle tree database, etc). -The Node also exposes methods that are consumed by the client (see `pxe`), such as querying network info or submitting a transaction. As Aztec evolves beyond local development, these methods will be accessible via a JSON-RPC API or similar. Refer to the `end-to-end` tests for examples on how to initialize an Aztec Node and use it along with a Private eXecution Service (PXE). +The Node also exposes methods that are consumed by the client (see `pxe`), such as querying network info or submitting a transaction. As Aztec evolves beyond local development, these methods will be accessible via a JSON-RPC API or similar. Refer to the `end-to-end` tests for examples on how to initialize an Aztec Node and use it along with a Private eXecution Environment (PXE). ## Development diff --git a/yarn-project/end-to-end/src/fixtures/utils.ts b/yarn-project/end-to-end/src/fixtures/utils.ts index be38f6d18cf..43aae8bc26f 100644 --- a/yarn-project/end-to-end/src/fixtures/utils.ts +++ b/yarn-project/end-to-end/src/fixtures/utils.ts @@ -175,7 +175,7 @@ export async function setupPXEService( * @param account - The account for use in create viem wallets. * @param config - The aztec Node Configuration * @param logger - The logger to be used - * @returns Private eXecution Service (PXE) client, viem wallets, contract addreses etc. + * @returns Private eXecution Environment (PXE) client, viem wallets, contract addreses etc. */ async function setupWithSandbox(account: Account, config: AztecNodeConfig, logger: DebugLogger) { // we are setting up against the sandbox, l1 contracts are already deployed