fix paths

Author: critesjosh

docs/docs/developers/guides/smart_contracts/advanced/common_patterns.md

@@ -75,7 +75,7 @@ In this situation, try to mark the public function as `internal`. This ensures y
 
 ### Moving public data into the private domain
 
-See [partial notes](../../../../aztec/concepts/advanced/storage/partial_notes.md). Partial notes are how public balances are transferred to private [in the NFT contract](../../../tutorials/codealong/contract_tutorials/nft_contract.md).
+See [partial notes](../../../../aztec/concepts/advanced/storage/partial_notes.md). Partial notes are how public balances are transferred to private [in the NFT contract](../../../tutorials/contract_tutorials/nft_contract.md).
 
 ### Discovering my notes
 
@@ -110,7 +110,7 @@ Hence, it's necessary to add a "randomness" field to your note to prevent such a
 
 ### L1 -- L2 interactions
 
-Refer to [Token Portal codealong tutorial on bridging tokens between L1 and L2](../../../tutorials/codealong/js_tutorials/token_bridge.md) and/or [Uniswap smart contract example that shows how to swap on L1 using funds on L2](../../../tutorials/codealong/js_tutorials/uniswap/index.md). Both examples show how to:
+Refer to [Token Portal codealong tutorial on bridging tokens between L1 and L2](../../../tutorials/js_tutorials/token_bridge.md) and/or [Uniswap smart contract example that shows how to swap on L1 using funds on L2](../../../tutorials/js_tutorials/uniswap/index.md). Both examples show how to:
 
 1. L1 -> L2 message flow
 2. L2 -> L1 message flow
@@ -124,7 +124,7 @@ To send a note to someone, they need to have a key which we can encrypt the note
 There are several patterns here:
 
 1. Give the contract a key and share it amongst all participants. This leaks privacy, as anyone can see all the notes in the contract.
-2. `transfer_to_public` funds into the contract - this is used in the [Uniswap smart contract example where a user sends private funds into a Uniswap Portal contract which eventually withdraws to L1 to swap on L1 Uniswap](../../../tutorials/codealong/js_tutorials/uniswap/index.md). This works like Ethereum - to achieve contract composability, you move funds into the public domain. This way the contract doesn't even need keys.
+2. `transfer_to_public` funds into the contract - this is used in the [Uniswap smart contract example where a user sends private funds into a Uniswap Portal contract which eventually withdraws to L1 to swap on L1 Uniswap](../../../tutorials/js_tutorials/uniswap/index.md). This works like Ethereum - to achieve contract composability, you move funds into the public domain. This way the contract doesn't even need keys.
 
 There are several other designs we are discussing through [in this discourse post](https://discourse.aztec.network/t/how-to-handle-private-escrows-between-two-parties/2440) but they need some changes in the protocol or in our demo contract. If you are interested in this discussion, please participate in the discourse post!
 

docs/docs/developers/guides/smart_contracts/cross_chain_communication.md

@@ -94,7 +94,7 @@ Note that while the `secret` and the `content` are both hashed, they are actuall
 
 ### Token bridge example
 
-Computing the `content` must currently be done manually, as we are still adding a number of bytes utilities. A good example exists within the [Token bridge example (codealong tutorial)](../../tutorials/codealong/js_tutorials/token_bridge.md).
+Computing the `content` must currently be done manually, as we are still adding a number of bytes utilities. A good example exists within the [Token bridge example (codealong tutorial)](../../tutorials/js_tutorials/token_bridge.md).
 
 #include_code claim_public /noir-projects/noir-contracts/contracts/app/token_bridge_contract/src/main.nr rust
 
@@ -239,4 +239,4 @@ Designated callers are enforced at the contract level for contracts that are not
 
 ## Further reading
 
-Follow the [token bridge tutorial](../../tutorials/codealong/js_tutorials/token_bridge.md) for hands-on experience writing and deploying a Portal contract.
+Follow the [token bridge tutorial](../../tutorials/js_tutorials/token_bridge.md) for hands-on experience writing and deploying a Portal contract.

docs/docs/developers/guides/smart_contracts/define_functions.md

@@ -63,7 +63,4 @@ You can set multiple functions as an initializer function simply by annotating e
 
 Calling any one of the functions annotated with `#[initializer]` will mark the contract as initialized.
 
-To see an initializer in action, follow the [Counter codealong tutorial](../../tutorials/codealong/contract_tutorials/counter_contract.md).
-
-
-## Further Reading
+To see an initializer in action, follow the [Counter codealong tutorial](../../tutorials/contract_tutorials/counter_contract.md).

docs/docs/developers/tutorials/contract_tutorials/counter_contract.md

@@ -163,7 +163,7 @@ SERVE=1 aztec flamegraph target/counter-Counter.json increment
 
 Note the total gate count at the bottom of the image. The image is interactive; you can hover over different parts of the graph to see the full function name of the execution step and its gate count. This tool also provides insight into the low-level operations that are performed in the private function. Don't worry about the details of the internals of the function right now, just be aware that the more complex the function, the more gates it will use and try out the flamegraph tool on your own functions.
 
-Read more about [profiling transactions with the flamegraph tool](../../../guides/smart_contracts/advanced/profiling_transactions.md).
+Read more about [profiling transactions with the flamegraph tool](../../guides/smart_contracts/advanced/profiling_transactions.md).
 
 For more information about writing efficient private functions, see [this page](https://noir-lang.org/docs/explainers/explainer-writing-noir) of the Noir documentation.
 

docs/docs/developers/tutorials/contract_tutorials/crowdfunding_contract.md

@@ -202,7 +202,7 @@ Follow the account contract tutorial on the [next page](./write_accounts_contrac
 
 ### Optional: Learn more about concepts mentioned here
 
-- [Initializer functions](../../../guides/smart_contracts/define_functions.md#initializer-functions)
-- [Versions and Updating](../../../guides/local_env/sandbox.md#updating).
-- [Authorizing actions](../../../../aztec/concepts/advanced/authwit.md)
-- [Public logs](../../../guides/smart_contracts/how_to_emit_event.md)
+- [Initializer functions](../../guides/smart_contracts/define_functions.md#initializer-functions)
+- [Versions and Updating](../../guides/local_env/sandbox.md#updating).
+- [Authorizing actions](../../../aztec/concepts/advanced/authwit.md)
+- [Public logs](../../guides/smart_contracts/how_to_emit_event.md)

docs/docs/developers/tutorials/contract_tutorials/nft_contract.md

@@ -174,7 +174,7 @@ Below the dependencies, paste the following Storage struct:
 
 ## Custom Notes
 
-The contract storage uses a [custom note](../../../guides/smart_contracts/note_types.md) implementation. Custom notes are useful for defining your own data types. You can think of a custom note as a "chunk" of private data, the entire thing is added, updated or nullified (deleted) together. This NFT note is very simple and stores only the owner and the `token_id` and uses `randomness` to hide its contents.
+The contract storage uses a [custom note](../../guides/smart_contracts/note_types.md) implementation. Custom notes are useful for defining your own data types. You can think of a custom note as a "chunk" of private data, the entire thing is added, updated or nullified (deleted) together. This NFT note is very simple and stores only the owner and the `token_id` and uses `randomness` to hide its contents.
 
 Randomness is required because notes are stored as commitments (hashes) in the note hash tree. Without randomness, the contents of a note may be derived through brute force (e.g. without randomness, if you know my Aztec address, you may be able to figure out which note hash in the tree is mine by hashing my address with many potential `token_id`s).
 

docs/versioned_docs/version-v1.2.0/developers/guides/smart_contracts/writing_contracts/common_patterns/index.md

@@ -17,31 +17,45 @@ Similarly we have discovered some anti-patterns too (like privacy leakage) that
 We call this the "authentication witness" pattern or authwit for short.
 
 - Approve someone in private domain:
-```typescript title="authwit_to_another_sc" showLineNumbers 
+
+```typescript title="authwit_to_another_sc" showLineNumbers
 // 4. Give approval to bridge to burn owner's funds:
 const withdrawAmount = 9n;
 const authwitNonce = Fr.random();
 const burnAuthwit = await user1Wallet.createAuthWit({
   caller: l2Bridge.address,
-  action: l2Token.methods.burn_private(ownerAddress, withdrawAmount, authwitNonce),
+  action: l2Token.methods.burn_private(
+    ownerAddress,
+    withdrawAmount,
+    authwitNonce
+  ),
 });
 ```
-> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/yarn-project/end-to-end/src/e2e_cross_chain_messaging/token_bridge_private.test.ts#L71-L79" target="_blank" rel="noopener noreferrer">Source code: yarn-project/end-to-end/src/e2e_cross_chain_messaging/token_bridge_private.test.ts#L71-L79</a></sub></sup>
 
+> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/yarn-project/end-to-end/src/e2e_cross_chain_messaging/token_bridge_private.test.ts#L71-L79" target="_blank" rel="noopener noreferrer">Source code: yarn-project/end-to-end/src/e2e_cross_chain_messaging/token_bridge_private.test.ts#L71-L79</a></sub></sup>
 
 Here you approve a contract to burn funds on your behalf.
 
 - Approve in public domain:
-```typescript title="authwit_public_transfer_example" showLineNumbers 
+
+```typescript title="authwit_public_transfer_example" showLineNumbers
 const action = asset
   .withWallet(wallets[1])
-  .methods.transfer_in_public(accounts[0].address, accounts[1].address, amount, authwitNonce);
+  .methods.transfer_in_public(
+    accounts[0].address,
+    accounts[1].address,
+    amount,
+    authwitNonce
+  );
 
-const validateActionInteraction = await wallets[0].setPublicAuthWit({ caller: accounts[1].address, action }, true);
+const validateActionInteraction = await wallets[0].setPublicAuthWit(
+  { caller: accounts[1].address, action },
+  true
+);
 await validateActionInteraction.send().wait();
 ```
-> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/yarn-project/end-to-end/src/e2e_token_contract/transfer_in_public.test.ts#L69-L76" target="_blank" rel="noopener noreferrer">Source code: yarn-project/end-to-end/src/e2e_token_contract/transfer_in_public.test.ts#L69-L76</a></sub></sup>
 
+> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/yarn-project/end-to-end/src/e2e_token_contract/transfer_in_public.test.ts#L69-L76" target="_blank" rel="noopener noreferrer">Source code: yarn-project/end-to-end/src/e2e_token_contract/transfer_in_public.test.ts#L69-L76</a></sub></sup>
 
 Here you approve someone to transfer funds publicly on your behalf
 
@@ -51,7 +65,7 @@ E.g. you don't want a user to subscribe once they have subscribed already. Or yo
 
 Emit a nullifier in your function. By adding this nullifier into the tree, you prevent another nullifier from being added again. This is also why in authwit, we emit a nullifier, to prevent someone from reusing their approval.
 
-```rust title="verify_private_authwit" showLineNumbers 
+```rust title="verify_private_authwit" showLineNumbers
 pub fn verify_private_authwit(self, inner_hash: Field) -> Field {
     // The `inner_hash` is "siloed" with the `msg_sender` to ensure that only it can
     // consume the message.
@@ -67,8 +81,8 @@ pub fn verify_private_authwit(self, inner_hash: Field) -> Field {
     IS_VALID_SELECTOR
 }
 ```
-> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/noir-projects/aztec-nr/aztec/src/authwit/account.nr#L72-L87" target="_blank" rel="noopener noreferrer">Source code: noir-projects/aztec-nr/aztec/src/authwit/account.nr#L72-L87</a></sub></sup>
 
+> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/noir-projects/aztec-nr/aztec/src/authwit/account.nr#L72-L87" target="_blank" rel="noopener noreferrer">Source code: noir-projects/aztec-nr/aztec/src/authwit/account.nr#L72-L87</a></sub></sup>
 
 Note be careful to ensure that the nullifier is not deterministic and that no one could do a preimage analysis attack. More in [the anti pattern section on deterministic nullifiers](#deterministic-nullifiers)
 
@@ -124,7 +138,7 @@ When you send someone a note, the note hash gets added to the note hash tree. To
 1. When sending someone a note, emit the note log to the recipient (the function encrypts the log in such a way that only a recipient can decrypt it). PXE then tries to decrypt all the encrypted logs, and stores the successfully decrypted one. [More info here](../how_to_emit_event.md)
 2. Manually delivering it via a custom contract method, if you choose to not emit logs to save gas or when creating a note in the public domain and want to consume it in private domain (`encrypt_and_emit_note` shouldn't be called in the public domain because everything is public), like in the previous section where we created a note in public that doesn't have a designated owner.
 
-```typescript title="offchain_delivery" showLineNumbers 
+```typescript title="offchain_delivery" showLineNumbers
 const txEffects = await pxe.getTxEffect(txHash);
 await contract.methods
   .deliver_transparent_note(
@@ -134,16 +148,16 @@ await contract.methods
     txHash.hash,
     txEffects!.data.noteHashes,
     txEffects!.data.nullifiers[0],
-    recipient,
+    recipient
   )
   .simulate();
 ```
-> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/yarn-project/end-to-end/src/composed/e2e_persistence.test.ts#L358-L371" target="_blank" rel="noopener noreferrer">Source code: yarn-project/end-to-end/src/composed/e2e_persistence.test.ts#L358-L371</a></sub></sup>
 
+> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/yarn-project/end-to-end/src/composed/e2e_persistence.test.ts#L358-L371" target="_blank" rel="noopener noreferrer">Source code: yarn-project/end-to-end/src/composed/e2e_persistence.test.ts#L358-L371</a></sub></sup>
 
 Note that this requires your contract to have a utility function that processes these notes and adds them to PXE.
 
-```rust title="deliver_note_contract_method" showLineNumbers 
+```rust title="deliver_note_contract_method" showLineNumbers
 // We cannot replace this function with the standard `process_message` function because the transparent note
 // originates in public and hence we cannot emit it as an offchain message. We could construct the offchain message
 // "manually" and then pass it to the `process_message` function, but this doesn't seem to be worth the effort
@@ -159,8 +173,8 @@ unconstrained fn deliver_transparent_note(
     recipient: AztecAddress,
 ) {
 ```
-> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/noir-projects/noir-contracts/contracts/app/token_blacklist_contract/src/main.nr#L301-L316" target="_blank" rel="noopener noreferrer">Source code: noir-projects/noir-contracts/contracts/app/token_blacklist_contract/src/main.nr#L301-L316</a></sub></sup>
 
+> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/noir-projects/noir-contracts/contracts/app/token_blacklist_contract/src/main.nr#L301-L316" target="_blank" rel="noopener noreferrer">Source code: noir-projects/noir-contracts/contracts/app/token_blacklist_contract/src/main.nr#L301-L316</a></sub></sup>
 
 ### Revealing encrypted logs conditionally
 
@@ -178,7 +192,7 @@ Notes are hashed and stored in the merkle tree. While notes do have a header wit
 
 Hence, it's necessary to add a "randomness" field to your note to prevent such attacks.
 
-```rust title="address_note_def" showLineNumbers 
+```rust title="address_note_def" showLineNumbers
 #[note]
 #[derive(Eq)]
 pub struct AddressNote {
@@ -198,8 +212,8 @@ impl AddressNote {
     }
 }
 ```
-> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/noir-projects/aztec-nr/address-note/src/address_note.nr#L5-L24" target="_blank" rel="noopener noreferrer">Source code: noir-projects/aztec-nr/address-note/src/address_note.nr#L5-L24</a></sub></sup>
 
+> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/noir-projects/aztec-nr/address-note/src/address_note.nr#L5-L24" target="_blank" rel="noopener noreferrer">Source code: noir-projects/aztec-nr/address-note/src/address_note.nr#L5-L24</a></sub></sup>
 
 ### L1 -- L2 interactions
 
@@ -243,7 +257,7 @@ E.g. for a voting contract, if your nullifier simply emits just the `user_addres
 
 Here is an example from the voting contract:
 
-```rust title="cast_vote" showLineNumbers 
+```rust title="cast_vote" showLineNumbers
 #[private]
 // annotation to mark function as private and expose private context
 fn cast_vote(candidate: Field) {
@@ -257,5 +271,5 @@ fn cast_vote(candidate: Field) {
     );
 }
 ```
-> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/noir-projects/noir-contracts/contracts/app/easy_private_voting_contract/src/main.nr#L38-L51" target="_blank" rel="noopener noreferrer">Source code: noir-projects/noir-contracts/contracts/app/easy_private_voting_contract/src/main.nr#L38-L51</a></sub></sup>
 
+> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v1.2.0/noir-projects/noir-contracts/contracts/app/easy_private_voting_contract/src/main.nr#L38-L51" target="_blank" rel="noopener noreferrer">Source code: noir-projects/noir-contracts/contracts/app/easy_private_voting_contract/src/main.nr#L38-L51</a></sub></sup>