Add a --playground flag on op-rbuilder to start with the flags required to run the builder on playground#49
Conversation
…ed to run the builder on playground Issue: #9 This change adds the ability to autoconfigure op-rbuilder to run a locally deployed builder-playground. Follow the instructions on how to start a builder playground under this repo: https://github.com/SozinM/builder-playground/tree/msozin/feat/flashblocks Now we can use the following startup parameters for op-rbuilder: - `./op-rbuilder node --builder.playground` This will start using the default $HOME/.playground/devnet directory - `./op-rbuilder node --builder.playground=<PATH>` Will use the provided path as the working directory of the playground
|
let's just create Makefile (Justfile) command to run it? |
done |
|
Sorry, wasn't clear enough |
No problem. I think that the logic of extracting the playground settings is too complex to be placed in a shell script. No strong opinions either, but if you don't mind I'd keep it now and revisit in a future PR when reintegrating flashblocks. |
|
Can you update README on how to use it? |
done |
Issue: #9
This change adds the ability to autoconfigure op-rbuilder to run a locally deployed builder-playground.
Follow the instructions on how to start a builder playground under this repo: https://github.com/flashbots/builder-playground
Now we can use the following startup parameters for op-rbuilder:
./op-rbuilder node --builder.playgroundThis will start using the default$HOME/.playground/devnetdirectory./op-rbuilder node --builder.playground=<PATH>Will use the provided path as the working directory of the playgroundYou can also use
just run-playgroundcommand that will automatically buildop-rbuilderwith the right features enabled and run it in playground mode.✅ I have completed the following steps:
make lintmake test