Remove kurtosis devnet from rollup-boost (#457)

Author: avalonche

.github/workflows/rb-kurtosis-integration-tests.yml

@@ -1,20 +1,7 @@
-kurtosis-devnet-up: build kurtosis-spawn
-
-kurtosis-devnet-down:
-    kurtosis enclave rm -f op-rollup-boost
-    kurtosis clean
-
-kurtosis-stress-test:
-    chmod +x ./scripts/ci/kurtosis.sh \
-        && ./scripts/ci/kurtosis.sh run
-
 # Build docker image (release)
 build:
     docker buildx build --build-arg RELEASE=true -t flashbots/rollup-boost:develop .
 
 # Build docker image (debug)
 build-debug:
-    docker buildx build --build-arg RELEASE=false -t flashbots/rollup-boost:develop .
-
-kurtosis-spawn:
-    kurtosis run github.com/ethpandaops/optimism-package@452133367b693e3ba22214a6615c86c60a1efd5e --args-file ./scripts/ci/kurtosis-params.yaml --enclave op-rollup-boost
+    docker buildx build --build-arg RELEASE=false -t flashbots/rollup-boost:develop .

Justfile

@@ -198,30 +198,6 @@ rollup-boost debug set-execution-mode [enabled|dry-run|disabled]
 - [@0xKitsune](https://github.com/0xKitsune)
 - [Eric Woolsey](https://github.com/0xForerunner)
 
-### Rollup Boost Devnet
-
-To run rollup-boost in an op-stack devnet first make sure you have [just](https://github.com/casey/just), and [kurtosis-cli](https://docs.kurtosis.com/install/) installed.
-
-Then run the following command to start the devnet:
-
-```sh
-just kurtosis-devnet-up
-```
-
-To stop the devnet run:
-
-```sh
-just kurtosis-devnet-down
-```
-
-To run a stress test against the devnet with [contender](https://github.com/flashbots/contender) first make sure you have docker installed.
-
-Then run the following command:
-
-```sh
-just kurtosis-stress-test
-```
-
 ## License
 
 The code in this project is free software under the [MIT License](/LICENSE).

README.md

@@ -60,7 +60,7 @@ For more details on the design philosophy and testing strategy of Rollup Boost,
 
 Rollup Boost underwent a security audit on May 11, 2025, with [Nethermind](https://www.nethermind.io). See the full report [here](https://github.com/flashbots/rollup-boost/blob/main/docs/NM_0411_0491_Security_Review_World_Rollup_Boost.pdf).
 
-In addition to the audit, we have an extensive suite of integration and kurtosis tests in our CI to ensure the whole flow works end-to-end with the OP stack as well as with external builders.
+In addition to the audit, we have an extensive suite of integration tests in our CI to ensure the whole flow works end-to-end with the OP stack as well as with external builders.
 
 ## Getting Help
 

book/src/intro.md

@@ -1,6 +1,6 @@
 # Running Rollup Boost Locally
 
-To run a local development network, you can use either Kurtosis or builder-playground to spin up the op-stack with rollup-boost.
+To run a local development network, you can use builder-playground to spin up the op-stack with rollup-boost.
 
 ## Builder Playground
 
@@ -26,36 +26,3 @@ In this setup, there is a prefunded test account to send test transactions to:
 - address: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266
 - private key: ac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80
 
-## Kurtosis
-
-Kurtosis is a tool to manage containerized services. To run rollup-boost in an op-stack devnet, first make sure you have [just](https://github.com/casey/just) and [kurtosis-cli](https://docs.kurtosis.com/install/) installed.
-
-This would include spinning up:
-
-- sequencer `op-node` and `op-geth`
-- builder `op-node` and `op-rbuilder`
-- rollup boost `rollup-boost`
-- ethereum l1 devnet with l2 contracts deployed
-- `op-proposer` and `op-batcher`
-
-Then run the following command to start the devnet:
-
-```sh
-just devnet-up
-```
-
-To stop the devnet run:
-
-```sh
-just devnet-down
-```
-
-To run a stress test against the devnet with [contender](https://github.com/flashbots/contender), first make sure you have Docker installed.
-
-Then run the following command:
-
-```sh
-just stress-test
-```
-
-See the [optimism package](https://github.com/ethpandaops/optimism-package/blob/main/README.md#configuration) for additional configuration options.

book/src/operators/local.md

@@ -29,4 +29,4 @@ We employ a layered testing strategy that provides defense in depth:
 
 Each integration test creates a complete test environment with mock L2 and builder nodes, simulating real-world scenarios that exercise the system's resilience features. One limitation of this approach is that issues in the mock CL node might not surface in these tests, offering quick feedback but potentially missing certain edge cases.
 
-**End-to-End Tests** (planned) will use actual components in a production-like environment. These tests using Kurtosis or Builder Playground will help ensure our test assumptions match real-world behavior.
+**End-to-End Tests** (planned) will use actual components in a production-like environment. These tests using Builder Playground will help ensure our test assumptions match real-world behavior.