Merge branch 'master' into route-thru-sm

.gitignore

@@ -7,6 +7,11 @@ dist/
 # Ignore environment-specific files
 .env
 
+# Ignore nixos related environment-specific files
+.envrc
+.cargo/
+.direnv/
+
 # Ignore editor-specific files
 .vscode/
 .idea/
@@ -25,4 +30,4 @@ target/
 debug/
 
 yarn.lock
-contracts/deployments/
+contracts/deployments/

README.md

@@ -20,6 +20,10 @@ That's it. This simple flow highlights some of the core mechanics of how AVSs wo
 
 The following instructions explain how to manually deploy the AVS from scratch including EigenLayer and AVS specific contracts using Foundry (forge) to a local anvil chain, and start Typescript Operator application and tasks.
 
+## Development Environment
+This section describes the tooling required for local development.
+
+### Non-Nix Environment
 Install dependencies:
 
 - [Node](https://nodejs.org/en/download/)
@@ -30,6 +34,15 @@ Install dependencies:
 - [Foundry](https://getfoundry.sh/)
 - [ethers](https://www.npmjs.com/package/ethers)
 
+### Nix Environment 
+On [Nix](https://nixos.org/) platforms, if you already have the proper Nix configuration, you can build the project’s artifacts inside a `nix develop` shell
+``` sh
+nix develop
+```
+Otherwise, please refer to [installed and configured](./docs/nix-setup-guide.md) section.
+
+## Quick start
+
 ### Start Anvil Chain
 
 In terminal window #1, execute the following commands:
@@ -93,14 +106,6 @@ For help and support deploying and modifying this repo for your AVS, please:
     * Ensure contracts are verified on Holesky. Eg `forge verify-contract --chain-id 17000 --num-of-optimizations 200 src/YourContract.sol:YourContract YOUR_CONTRACT_ADDRESS`
     * Send us your transaction hash where your contract is failing. We will use Tenderly to debug (adjust gas limit) and/or cast to re-run the transaction (eg `cast call --trace "trace_replayTransaction(0xTransactionHash)"`).
 
-- Local anvil testing:
-  - Recompile the contracts with the `--revert-strings debug` flag. Deploy the contracts again and retest.
-  - Include the full stacktrace from your error as a .txt file attachment.
-  - Create a minimal repo that demonstrates the behavior (fork or otherwise).
-  - Steps require to reproduce issue (compile and cause the error).
-- Holesky testing:
-  - Ensure contracts are verified on Holesky. Eg `forge verify-contract --chain-id 17000 --num-of-optimizations 200 src/YourContract.sol:YourContract YOUR_CONTRACT_ADDRESS`
-  - Send us your transaction hash where your contract is failing. We will use Tenderly to debug (adjust gas limit) and/or cast to re-run the transaction (eg `cast call --trace "trace_replayTransaction(0xTransactionHash)"`).
 
 ### Contact Us
 

docs/nix-setup-guide.md

@@ -0,0 +1,145 @@
+# Nix Setup Guide 
+
+Here you will find instructions on how to install and configure [nix package manager](https://nixos.wiki/wiki/Nix_package_manager) to work with 
+projects.
+
+## Installing / Upgrading 
+
+If you don't have nix installed, follow the instructions on the 
+[official website](https://nixos.org/download), or simply use one of following
+commands in a terminal:
+
+- For multi-user installation (i.e., system-wide setup, **recommended**)
+```bash
+sh <(curl -L https://nixos.org/nix/install) --daemon
+```
+- For single-user installation (i.e., local setup)
+```bash 
+sh <(curl -L https://nixos.org/nix/install) --no-daemon
+```
+
+We use nix `flakes` which require nix version `>= 2.4`, therefore if you already 
+have nix installed, make sure to 
+[upgrade](https://nixos.org/manual/nix/stable/installation/upgrading) to a 
+recent version.
+
+## Becoming a Truster User
+
+If you are on NixOS or have installed nix in multi-user mode, you **must** be 
+a [trusted user](https://nixos.org/nix/manual/#ssec-multi-user), which is 
+necessary to enable access to our binary cache.
+
+On non-NixOS systems, append the following line to the system-wide configuration 
+`/etc/nix/nix.conf`:
+```txt
+trusted-users = USER root
+```
+**Where `USER` is the result of running `whoami` in a terminal.**
+
+You can also use a group name by prefixing it with `@`. For instance, to add all 
+members of the `wheel` group:
+```txt
+trusted-users = @wheel root
+```
+
+On NixOS, add the user/group name to the list under 
+[`nix.settings.trusted-users`](https://search.nixos.org/options?show=nix.settings.trusted-users).
+
+## Setting Up for Flakes
+
+We use [Nix flakes](https://nixos.wiki/wiki/Flakes). To configure for flakes, follow the instruction  on the [Nixos Wiki](https://nixos.wiki/wiki/Flakes) or simply do one of the following depending on your system:
+
+- On non-NixOS systems, edit one of the following two files (create them if they don't exist):
+   - `/etc/nix/nix.conf` for system-wide settings on a multi-user installation 
+   - `~/.config/nix/nix.conf` for user-wide settings on a single-user installation
+
+By appending the following lines:
+```txt
+experimental-features = nix-command flakes
+```
+
+On NixOS systems, set the following NixOS options:
+```nix
+ nix.settings.experimental-features = [ "nix-command" "flakes" ];
+```
+
+## Notes for Apple Users
+
+Apple Silicon users can run any Intel binary out-of-the-box thanks to Rosetta
+emulation, but when working with nix flakes, the `aarch64-darwin` system will be
+selected by default.
+
+However, some projects at cannot be built natively on `aarch64-darwin`.
+
+Therefore you must specify the `--system` explicitly to target `x86_64-darwin`.
+```bash
+nix (develop|build|run|check) --system x86_64-darwin # Will use the x86_64-darwin derivation
+nix (develop|build|run|check) # Will use the aarch64-darwin derivation, if available
+```
+
+To enable this, you must append the following lines to your `/etc/nix/nix.conf` 
+or `~/.config/nix/nix.conf`:
+```txt
+extra-platforms = x86_64-darwin aarch64-darwin
+extra-sandbox-paths = /System/Library/Frameworks /System/Library/PrivateFrameworks /usr/lib /private/tmp /private/var/tmp /usr/bin/env
+```
+
+You may need to reload the nix daemon for changes to take effect:
+```bash
+sudo launchctl stop org.nixos.nix-daemon
+sudo launchctl start org.nixos.nix-daemon
+```
+
+## Development Shell and VSCode 
+
+Now that you have nix installed and configured, you may enter the development 
+shell:
+```
+nix develop
+```
+If you are on Apple Silicon and a native shell is not available, you will want 
+to run this instead:
+```
+nix develop --system x86_64-darwin
+```
+
+If you are a `VSCode` user, you may also start your development session by 
+executing the following command:
+```
+nix develop --command code
+```
+
+If you are running `nix develop` for the first time, please enter `y` at the 
+following prompts to create the local nix settings file 
+`~/.local/share/nix/trusted-settings.json`:
+```txt  
+> do you want to allow configuration setting 'accept-flake-config' to be set to 'true' (y/N)?
+> do you want to permanently mark this value as trusted (y/N)?
+```
+
+It is particularly important to accept the `extra-substituters` and 
+`extra-trusted-public-keys` settings as these will grant access to our binary 
+cache.
+
+When `nix develop` is run for the first time, a significant amount of 
+dependencies will be downloaded, built and installed. This process may take a 
+couple of hours but is expected to happen only once. However, if you ever 
+witness that GHC is also being built from scratch, then it is likely that your 
+binary cache has not been configured properly or is not being considered.
+Accepting the configuration settings as outlined above should be sufficient to 
+avoid this. Nevertheless, if your caches are still broken, you'll want to review
+this document carefully to ensure that your nix installation is properly 
+configured.
+
+You will know that your caches are broken if you see this message:
+```
+warning: ignoring untrusted substituter 'https://cache.iog.io', you are not a trusted user.
+```
+
+If is possible that your settings are correct but the nix daemon is not properly 
+considering them. In this case, stop the `nix develop` process and restart the 
+`nix-daemon` as follows:
+```bash 
+sudo systemctl stop nix-daemon.service
+``` 
+Once done, you can launch the `nix develop` process again.