From e835c284f553f711602dd79e6cee115f8ba39798 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=A1s=20Venturo?= Date: Mon, 15 Jan 2024 15:27:46 -0300 Subject: [PATCH 1/4] Clarify installation vs sandbox command --- docs/docs/dev_docs/getting_started/quickstart.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/dev_docs/getting_started/quickstart.md b/docs/docs/dev_docs/getting_started/quickstart.md index b5120e84489..9a58e7334ff 100644 --- a/docs/docs/dev_docs/getting_started/quickstart.md +++ b/docs/docs/dev_docs/getting_started/quickstart.md @@ -53,7 +53,7 @@ Once these have been installed, to start the sandbox, run: aztec-sandbox ``` -This will attempt to run the Sandbox on ` localhost:8080`, so you will have to make sure nothing else is running on that port or change the port defined in `./.aztec/docker-compose.yml`. Running the command again will overwrite any changes made to the `docker-compose.yml`. +This will attempt to run the Sandbox on ` localhost:8080`, so you will have to make sure nothing else is running on that port or change the port defined in `./.aztec/docker-compose.yml`. Running the installation again will overwrite any changes made to the `docker-compose.yml`. This command will also install the CLI if a node package version of the CLI isn't found locally. From 464d90aac7b64657b2f3475bd6a080dcffc66252 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=A1s=20Venturo?= Date: Mon, 15 Jan 2024 15:50:05 -0300 Subject: [PATCH 2/4] Remove duplicate private state intro --- docs/docs/concepts/foundation/state_model/main.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/docs/docs/concepts/foundation/state_model/main.md b/docs/docs/concepts/foundation/state_model/main.md index 36ca4515c3f..088e6e13199 100644 --- a/docs/docs/concepts/foundation/state_model/main.md +++ b/docs/docs/concepts/foundation/state_model/main.md @@ -12,18 +12,6 @@ Internal to the Aztec network, public state is stored and updated by the sequenc ## Private State -Every smart contract needs a way to track information over time - that's what state is. In order to have both private and public transactions and storage in Aztec, we have to have public and private state. - -On this page, you’ll learn - -- Aztec's unique interpretation of private state -- Representation of private state in an append-only database -- Concept of 'deleting' private state variables using nullifiers -- How to modify private state -- How Aztec abstracts the UTXO model from developers - -## Private State on Aztec - Private state must be treated differently from public state and this must be expressed in the semantics of Aztec.nr. Private state is encrypted and therefore is "owned" by a user or a set of users (via shared secrets) that are able to decrypt the state. From b1e4845a4003bdbb263f8a42b148e29a60c8661d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=A1s=20Venturo?= Date: Mon, 15 Jan 2024 15:50:56 -0300 Subject: [PATCH 3/4] Fix typo --- docs/docs/concepts/foundation/state_model/main.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/concepts/foundation/state_model/main.md b/docs/docs/concepts/foundation/state_model/main.md index 088e6e13199..b856e0c2ef3 100644 --- a/docs/docs/concepts/foundation/state_model/main.md +++ b/docs/docs/concepts/foundation/state_model/main.md @@ -20,7 +20,7 @@ Private state is represented in an append-only database since updating a record The act of "deleting" a private state variable can be represented by adding an associated nullifier to a nullifier set. The nullifier is generated such that, without knowing the decryption key of the owner, an observer cannot link a state record with a nullifier. -Modification of state variables can be emulated by nullifying the a state record and creating a new record to represent the variable. Private state has an intrinsic UTXO structure and this must be represented in the language semantics of manipulating private state. +Modification of state variables can be emulated by nullifying the state record and creating a new record to represent the variable. Private state has an intrinsic UTXO structure and this must be represented in the language semantics of manipulating private state. ### Abstracting UTXO's from App's / Users From 9eca0c610b077fe732c3489611c61c14b39385f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=A1s=20Venturo?= Date: Tue, 16 Jan 2024 12:10:57 -0300 Subject: [PATCH 4/4] Add non-default port CLI hint --- docs/docs/dev_docs/getting_started/quickstart.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/docs/dev_docs/getting_started/quickstart.md b/docs/docs/dev_docs/getting_started/quickstart.md index 9a58e7334ff..4d05ec44d04 100644 --- a/docs/docs/dev_docs/getting_started/quickstart.md +++ b/docs/docs/dev_docs/getting_started/quickstart.md @@ -71,6 +71,10 @@ Start by deploying a token contract. After it is deployed, we check that the dep #include_code deploy yarn-project/end-to-end/src/guides/up_quick_start.sh bash +:::note +If you're not using the default port for the Sandbox, make sure to pass the `--rpc-url` parameter, e.g.: `--rpc-url http://localhost:8000`. +::: + Note that the deployed contract address is exported, so we can use it as `$CONTRACT` later on. ## Call a contract with the CLI