create-stylus 1.1.0

package/templates/base/.yarnrc.yml

@@ -0,0 +1,11 @@
+enableColors: true
+
+nmHoistingLimits: workspaces
+
+nodeLinker: node-modules
+
+plugins:
+  - path: .yarn/plugins/@yarnpkg/plugin-typescript.cjs
+    spec: "@yarnpkg/plugin-typescript"
+
+yarnPath: .yarn/releases/yarn-3.2.3.cjs

package/templates/base/CONTRIBUTING.md

@@ -0,0 +1,86 @@
+# Welcome to Scaffold-Stylus Contributing Guide
+
+Thank you for investing your time in contributing to Scaffold-Stylus!
+
+This guide aims to provide an overview of the contribution workflow to help us make the contribution process effective for everyone involved.
+
+## About the Project
+
+Scaffold-Stylus is a minimal and forkable repo providing builders with a starter kit to build decentralized applications on Ethereum.
+
+Read the [README](README.md) to get an overview of the project.
+
+### Vision
+
+The goal of Scaffold-Stylus is to provide the primary building blocks for a decentralized application.
+
+The repo can be forked to include integrations and more features, but we want to keep the master branch simple and minimal.
+
+### Project Status
+
+The project is under active development.
+
+You can view the open Issues, follow the development process and contribute to the project.
+
+## Getting started
+
+You can contribute to this repo in many ways:
+
+- Solve open issues
+- Report bugs or feature requests
+- Improve the documentation
+
+Contributions are made via Issues and Pull Requests (PRs). A few general guidelines for contributions:
+
+- Search for existing Issues and PRs before creating your own.
+- Contributions should only fix/add the functionality in the issue OR address style issues, not both.
+- If you're running into an error, please give context. Explain what you're trying to do and how to reproduce the error.
+- Please use the same formatting in the code repository. You can configure your IDE to do it by using the prettier / linting config files included in each package.
+- If applicable, please edit the README.md file to reflect the changes.
+
+### Issues
+
+Issues should be used to report problems, request a new feature, or discuss potential changes before a PR is created.
+
+#### Solve an issue
+
+Scan through our [existing issues](https://github.com/Arb-Stylus/scaffold-stylus/issues) to find one that interests you.
+
+If a contributor is working on the issue, they will be assigned to the individual. If you find an issue to work on, you are welcome to assign it to yourself and open a PR with a fix for it.
+
+#### Create a new issue
+
+If a related issue doesn't exist, you can open a new issue.
+
+Some tips to follow when you are creating an issue:
+
+- Provide as much context as possible. Over-communicate to give the most details to the reader.
+- Include the steps to reproduce the issue or the reason for adding the feature.
+- Screenshots, videos etc., are highly appreciated.
+
+### Pull Requests
+
+#### Pull Request Process
+
+We follow the ["fork-and-pull" Git workflow](https://github.com/susam/gitpr)
+
+1. Fork the repo
+2. Clone the project
+3. Create a new branch with a descriptive name
+4. Commit your changes to the new branch
+5. Push changes to your fork
+6. Open a PR in our repository and tag one of the maintainers to review your PR
+
+Here are some tips for a high-quality pull request:
+
+- Create a title for the PR that accurately defines the work done.
+- Structure the description neatly to make it easy to consume by the readers. For example, you can include bullet points and screenshots instead of having one large paragraph.
+- Add the link to the issue if applicable.
+- Have a good commit message that summarises the work done.
+
+Once you submit your PR:
+
+- We may ask questions, request additional information or ask for changes to be made before a PR can be merged. Please note that these are to make the PR clear for everyone involved and aims to create a frictionless interaction process.
+- As you update your PR and apply changes, mark each conversation resolved.
+
+Once the PR is approved, we'll "squash-and-merge" to keep the git commit history clean.

package/templates/base/LICENCE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 BuidlGuidl
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/templates/base/nitro-devnode/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/templates/base/nitro-devnode/README.md

@@ -0,0 +1,70 @@
+# Nitro dev node
+
+This repository contains a simple script to start a Nitro dev node and deploy the Stylus `Cache Manager` contract for testing purposes.
+
+## Prerequisites
+
+Before beginning, ensure the following is installed and running on your machine:
+
+- Docker: Required to run the Nitro dev node in a container. Install Docker by following [the official installation guide](https://docs.docker.com/get-started/get-docker/) for your operating system.
+- cast: A command-line tool from Foundry for interacting with Ethereum smart contracts. You can install it via Foundry by following [the installation instructions](https://book.getfoundry.sh/getting-started/installation).
+- jq: A lightweight JSON parsing tool used to extract contract addresses from the script output. Install jq by following [the official installation guide](https://jqlang.github.io/jq/download/) for your operating system.
+
+## Development account (used by default)
+
+In `--dev` mode, the script uses a pre-funded development account by default. This account is pre-funded with ETH in all networks and is used to deploy contracts, interact with the chain, and assume chain ownership.
+
+- Address: 0x3f1Eae7D46d88F08fc2F8ed27FCb2AB183EB2d0E
+- Private key: 0xb6b15c8cb491557369f3c7d2c287b053eb229daa9c22138887752191c9520659
+
+You don’t need to set up a private key manually unless you prefer using your own key.
+ 
+
+## Chain ownership in `--dev` mode
+
+In Nitro `--dev` mode, the default chain owner is set to `0x0000000000000000000000000000000000000000`. However, you can use the `ArbDebug` precompile to set the chain owner. This precompile includes the `becomeChainOwner()` function, which can be called to assume ownership of the chain.
+
+Chain ownership is important because it allows the owner to perform certain critical functions within the Arbitrum environment, such as:
+
+- Adding or removing other chain owners
+- Setting the L1 and L2 base fees directly
+- Adjusting the gas pricing inertia and backlog tolerance
+- Modifying the computational speed limit and transaction gas limits
+- Managing network and infrastructure fee accounts
+
+The script automatically sets the chain owner to the pre-funded dev account before registering the `Cache Manager` contract. Here’s how the `becomeChainOwner()` function is called within the script:
+
+```bash
+cast send 0x00000000000000000000000000000000000000FF "becomeChainOwner()" --private-key 0xb6b15c8cb491557369f3c7d2c287b053eb229daa9c22138887752191c9520659 --rpc-url http://127.0.0.1:8547
+```
+
+This step ensures that the dev account has ownership of the chain, which is necessary to register the `Cache Manager` as a WASM cache manager.
+
+
+## Usage
+
+To use the script, follow these steps:
+
+1. Clone the repository:
+
+```bash
+git clone https://github.com/OffchainLabs/nitro-devnode.git
+cd nitro-devnode
+```
+
+2. Run the dev node script:
+Run the script to start the Nitro dev node, deploy the Stylus `Cache Manager` contract, and register it as a WASM cache manager using the default development account:
+
+```bash
+./run-dev-node.sh
+```
+
+The script will:
+
+- Start the Nitro dev node in the background using Docker.
+- Deploy the Stylus `Cache Manager` contract on the local Nitro network.
+- Register the `Cache Manager` contract as a WASM cache manager.
+
+## Note on `--dev` mode
+
+The script starts the Nitro node in `--dev` mode, which does not persist chain data. Each time you restart the node, the chain state resets. This is suitable for testing and development purposes, but for persistent chain data, consider using a full node setup instead of `--dev`.

package/templates/base/nitro-devnode/run-dev-node.sh

@@ -0,0 +1,132 @@
+#!/bin/bash
+
+NITRO_NODE_VERSION="v3.5.5-90ee45c"  # <-- only update this when you need a new version
+TARGET_IMAGE="offchainlabs/nitro-node:${NITRO_NODE_VERSION}"
+
+RPC=http://127.0.0.1:8547
+PRIVATE_KEY=0xb6b15c8cb491557369f3c7d2c287b053eb229daa9c22138887752191c9520659
+CREATE2_FACTORY=0x4e59b44847b379578588920ca78fbf26c0b4956c
+SALT=0x0000000000000000000000000000000000000000000000000000000000000000
+
+# By default, use nitro docker image. If "--stylus" is passed, build the image with stylus dev dependencies
+STYLUS_MODE="false"
+
+# Parse arguments
+while [[ $# -gt 0 ]]; do
+  case "$1" in
+    --stylus)
+      STYLUS_MODE="true"
+      shift
+      ;;
+    *)
+      echo "Unknown option: $1"
+      exit 1
+      ;;
+  esac
+done
+
+if [[ "$STYLUS_MODE" == "true" ]]; then
+  echo "Building Nitro node with Stylus dev dependencies..."
+  # Build using the specific version
+  docker build . --target nitro-node-stylus-dev \
+  --tag nitro-node-stylus-dev  -f stylus-dev/Dockerfile \
+  --build-arg NITRO_NODE_VERSION="${NITRO_NODE_VERSION}"
+
+  TARGET_IMAGE="nitro-node-stylus-dev"
+fi
+
+# Start Nitro dev node in the background
+echo "Starting Nitro dev node..."
+docker run --rm --name nitro-dev -p 8547:8547 "${TARGET_IMAGE}" --dev --http.addr 0.0.0.0 --http.api=net,web3,eth,debug &
+
+# Kill background processes when exiting
+trap 'kill $(jobs -p) 2>/dev/null' EXIT
+
+# Wait for the node to initialize
+echo "Waiting for the Nitro node to initialize..."
+
+until [[ "$(curl -s -X POST -H "Content-Type: application/json" \
+  --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":1}' \
+  $RPC)" == *"result"* ]]; do
+    sleep 0.1
+done
+
+
+# Check if node is running
+curl_output=$(curl -s -X POST -H "Content-Type: application/json" \
+  --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":1}' \
+  $RPC)
+
+if [[ "$curl_output" == *"result"* ]]; then
+  echo "Nitro node is running!"
+else
+  echo "Failed to start Nitro node."
+  exit 1
+fi
+
+# Make the caller a chain owner
+echo "Setting chain owner to pre-funded dev account..."
+cast send 0x00000000000000000000000000000000000000FF "becomeChainOwner()" \
+  --private-key $PRIVATE_KEY \
+  --rpc-url $RPC
+
+# Set the L1 data fee to 0 so it doesn't impact the L2 Gas limit.
+# This makes the gas estimates closer to Ethereum and allows the deployment of the CREATE2 factory
+cast send -r $RPC --private-key $PRIVATE_KEY 0x0000000000000000000000000000000000000070 'setL1PricePerUnit(uint256)' 0x0
+
+# Deploy CREATE2 factory
+echo "Deploying the CREATE2 factory"
+cast send --rpc-url $RPC --private-key $PRIVATE_KEY --value "1 ether" 0x3fab184622dc19b6109349b94811493bf2a45362
+cast publish --rpc-url $RPC 0xf8a58085174876e800830186a08080b853604580600e600039806000f350fe7fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe03601600081602082378035828234f58015156039578182fd5b8082525050506014600cf31ba02222222222222222222222222222222222222222222222222222222222222222a02222222222222222222222222222222222222222222222222222222222222222
+if [ "$(cast code -r $RPC $CREATE2_FACTORY)" == "0x" ]; then
+  echo "Failed to deploy CREATE2 factory"
+  exit 1
+fi
+
+# Deploy Cache Manager Contract
+echo "Deploying Cache Manager contract..."
+deploy_output=$(cast send --private-key $PRIVATE_KEY \
+  --rpc-url $RPC \
+  --create 0x60a06040523060805234801561001457600080fd5b50608051611d1c61003060003960006105260152611d1c6000f3fe)
+
+# Extract contract address using awk from plain text output
+contract_address=$(echo "$deploy_output" | awk '/contractAddress/ {print $2}')
+
+# Check if contract deployment was successful
+if [[ -z "$contract_address" ]]; then
+  echo "Error: Failed to extract contract address. Full output:"
+  echo "$deploy_output"
+  exit 1
+fi
+
+echo "Cache Manager contract deployed at address: $contract_address"
+
+# Register the deployed Cache Manager contract
+echo "Registering Cache Manager contract as a WASM cache manager..."
+registration_output=$(cast send --private-key $PRIVATE_KEY \
+  --rpc-url $RPC \
+  0x0000000000000000000000000000000000000070 \
+  "addWasmCacheManager(address)" "$contract_address")
+
+# Check if registration was successful
+if [[ "$registration_output" == *"error"* ]]; then
+  echo "Failed to register Cache Manager contract. Registration output:"
+  echo "$registration_output"
+  exit 1
+fi
+echo "Cache Manager deployed and registered successfully"
+
+# Deploy StylusDeployer
+deployer_code=$(cat ./stylus-deployer-bytecode.txt)
+deployer_address=$(cast create2 --salt $SALT --init-code $deployer_code)
+cast send --private-key $PRIVATE_KEY --rpc-url $RPC \
+    $CREATE2_FACTORY "$SALT$deployer_code"
+if [ "$(cast code -r $RPC $deployer_address)" == "0x" ]; then
+  echo "Failed to deploy StylusDeployer"
+  exit 1
+fi
+echo "StylusDeployer deployed at address: $deployer_address"
+
+# If no errors, print success message
+echo "Nitro node is running..."
+wait  # Keep the script alive and the node running

package/templates/base/nitro-devnode/start-chain-with-cors.sh

@@ -0,0 +1,150 @@
+#!/bin/bash
+
+NITRO_NODE_VERSION="v3.5.5-90ee45c"
+TARGET_IMAGE="offchainlabs/nitro-node:${NITRO_NODE_VERSION}"
+
+RPC=http://127.0.0.1:8547
+PRIVATE_KEY=0xb6b15c8cb491557369f3c7d2c287b053eb229daa9c22138887752191c9520659
+CREATE2_FACTORY=0x4e59b44847b379578588920ca78fbf26c0b4956c
+SALT=0x0000000000000000000000000000000000000000000000000000000000000000
+
+# By default, use nitro docker image. If "--stylus" is passed, build the image with stylus dev dependencies
+STYLUS_MODE="false"
+
+# Parse arguments
+while [[ $# -gt 0 ]]; do
+  case "$1" in
+    --stylus)
+      STYLUS_MODE="true"
+      shift
+      ;;
+    *)
+      echo "Unknown option: $1"
+      exit 1
+      ;;
+  esac
+done
+
+# Check if nitro-devnode exists, if not initialize the submodule
+if [ ! -d "./nitro-devnode" ]; then
+  echo "nitro-devnode directory not found. Initializing nitro-devnode submodule..."
+  # Run git submodule from the root directory where .gitmodules is located
+  cd "$(git rev-parse --show-toplevel)" && git submodule update --init nitro-devnode && cd packages/stylus
+fi
+
+if [[ "$STYLUS_MODE" == "true" ]]; then
+  echo "Building Nitro node with Stylus dev dependencies..."
+  # Build using the specific version
+  docker build . --target nitro-node-stylus-dev \
+  --tag nitro-node-stylus-dev  -f nitro-devnode/stylus-dev/Dockerfile \
+  --build-arg NITRO_NODE_VERSION="${NITRO_NODE_VERSION}"
+
+  TARGET_IMAGE="nitro-node-stylus-dev"
+fi
+
+# Start Nitro dev node in the background with CORS settings and WebSocket enabled
+echo "Starting Nitro dev node with CORS and WebSocket enabled..."
+docker run --rm --name nitro-dev -p 8547:8547 "${TARGET_IMAGE}" --dev --http.addr 0.0.0.0 --http.api=net,web3,eth,debug --http.corsdomain="*" --http.vhosts="*" --ws.addr 0.0.0.0 --ws.port 8547 --ws.api=net,web3,eth,debug --ws.origins="*" &
+
+# Kill background processes when exiting
+trap 'kill $(jobs -p) 2>/dev/null' EXIT
+
+# Wait for the node to initialize
+echo "Waiting for the Nitro node to initialize..."
+
+until [[ "$(curl -s -X POST -H "Content-Type: application/json" \
+  --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":1}' \
+  $RPC)" == *"result"* ]]; do
+    sleep 0.1
+done
+
+# Check if node is running
+curl_output=$(curl -s -X POST -H "Content-Type: application/json" \
+  --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":1}' \
+  $RPC)
+
+if [[ "$curl_output" == *"result"* ]]; then
+  echo "Nitro node is running with CORS and WebSocket enabled!"
+  echo "HTTP RPC: http://127.0.0.1:8547"
+  echo "WebSocket: ws://127.0.0.1:8547"
+else
+  echo "Failed to start Nitro node."
+  exit 1
+fi
+
+# Make the caller a chain owner
+echo "Setting chain owner to pre-funded dev account..."
+cast send 0x00000000000000000000000000000000000000FF "becomeChainOwner()" \
+  --private-key $PRIVATE_KEY \
+  --rpc-url $RPC
+
+# Set the L1 data fee to 0 so it doesn't impact the L2 Gas limit.
+# This makes the gas estimates closer to Ethereum and allows the deployment of the CREATE2 factory
+cast send -r $RPC --private-key $PRIVATE_KEY 0x0000000000000000000000000000000000000070 'setL1PricePerUnit(uint256)' 0x0
+
+# Deploy CREATE2 factory
+echo "Deploying the CREATE2 factory"
+cast send --rpc-url $RPC --private-key $PRIVATE_KEY --value "1 ether" 0x3fab184622dc19b6109349b94811493bf2a45362
+cast publish --rpc-url $RPC 0xf8a58085174876e800830186a08080b853604580600e600039806000f350fe7fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe03601600081602082378035828234f58015156039578182fd5b8082525050506014600cf31ba02222222222222222222222222222222222222222222222222222222222222222a02222222222222222222222222222222222222222222222222222222222222222
+if [ "$(cast code -r $RPC $CREATE2_FACTORY 2>/dev/null)" == "0x" ]; then
+  echo "Failed to deploy CREATE2 factory"
+  exit 1
+fi
+
+# Deploy Cache Manager Contract
+echo "Deploying Cache Manager contract..."
+deploy_output=$(cast send --private-key $PRIVATE_KEY \
+  --rpc-url $RPC \
+  --create 0x60a06040523060805234801561001457600080fd5b50608051611d1c61003060003960006105260152611d1c6000f3fe)
+
+# Extract contract address using awk from plain text output
+contract_address=$(echo "$deploy_output" | awk '/contractAddress/ {print $2}')
+
+# Check if contract deployment was successful
+if [[ -z "$contract_address" ]]; then
+  echo "Error: Failed to extract contract address. Full output:"
+  echo "$deploy_output"
+  exit 1
+fi
+
+echo "Cache Manager contract deployed at address: $contract_address"
+
+# Register the deployed Cache Manager contract
+echo "Registering Cache Manager contract as a WASM cache manager..."
+registration_output=$(cast send --private-key $PRIVATE_KEY \
+  --rpc-url $RPC \
+  0x0000000000000000000000000000000000000070 \
+  "addWasmCacheManager(address)" "$contract_address")
+
+# Check if registration was successful
+if [[ "$registration_output" == *"error"* ]]; then
+  echo "Failed to register Cache Manager contract. Registration output:"
+  echo "$registration_output"
+  exit 1
+fi
+echo "Cache Manager deployed and registered successfully"
+
+# Deploy StylusDeployer
+deployer_code=$(cat ./nitro-devnode/stylus-deployer-bytecode.txt)
+deployer_address=$(cast create2 --init-code $deployer_code 2>/dev/null)
+cast send --private-key $PRIVATE_KEY --rpc-url $RPC \
+    $CREATE2_FACTORY "$SALT$deployer_code"
+if [ "$(cast code -r $RPC $deployer_address 2>/dev/null)" == "0x" ]; then
+  echo "Failed to deploy StylusDeployer"
+  exit 1
+fi
+echo "StylusDeployer deployed at address: $deployer_address"
+
+# Fund accounts with 1 ETH each
+echo "Funding accounts with 1 ETH each..."
+cast send --private-key $PRIVATE_KEY --rpc-url $RPC --value "1 ether" 0xDD09b55496EaA3cFAe23137ABDeA52a9a979B70e
+cast send --private-key $PRIVATE_KEY --rpc-url $RPC --value "1 ether" 0xE9cB1563bE49002383D08386ee287aF7BAD08c3b
+cast send --private-key $PRIVATE_KEY --rpc-url $RPC --value "1 ether" 0x838d568Ffb16BC74083e88fd769df85E8d3afcE6
+cast send --private-key $PRIVATE_KEY --rpc-url $RPC --value "1 ether" 0xA491d1134388c78AeEDf6b1Ca3F21657015Ff8E1
+echo "All accounts funded with 1 ETH each"
+
+# If no errors, print success message
+echo "Nitro node is running with CORS and WebSocket enabled..."
+echo "HTTP RPC: http://127.0.0.1:8547"
+echo "WebSocket: ws://127.0.0.1:8547"
+wait  # Keep the script alive and the node running