chore: update docs

bolt-spammer-helder/.env.example

@@ -1,5 +1,6 @@
-EL_PROVIDER_URL=https://rpc.helder-devnets.xyz
 BEACON_CLIENT_URL=
-REGISTRY_ADDRESS=0xdF11D829eeC4C192774F3Ec171D822f6Cb4C14d9
 PRIVATE_KEY=
-REGISTRY_ABI_PATH=./registry_abi.json
+
+# these can be used as defaults
+EL_PROVIDER_URL=https://rpc.helder-devnets.xyz
+REGISTRY_ADDRESS=0xdF11D829eeC4C192774F3Ec171D822f6Cb4C14d9

bolt-spammer-helder/README.md

@@ -3,15 +3,14 @@
 To run the spammer, make sure to set the following environment variables in a `.env` file:
 
 ```text
-EL_PROVIDER_URL=https://rpc.helder-devnets.xyz
-BEACON_CLIENT_URL=
-REGISTRY_ADDRESS=0xdF11D829eeC4C192774F3Ec171D822f6Cb4C14d9
-PRIVATE_KEY=
-REGISTRY_ABI_PATH=./registry_abi.json
+PRIVATE_KEY=<your account private key with ETH on Helder>
+BEACON_CLIENT_URL=<your beacon client HTTP endpoint>
 ```
 
 This template can be found in the `env.example` file.
 
-Then, just run the spammer with `cargo run`. It will fetch all the validators of the current epoch,
+Then, just run the spammer with `cargo run`.
+
+It will fetch all the validators of the current epoch,
 and try to send a pre-confirmation to the first one registered on the Bolt registry.
 If no validators are found, the program will gracefully exit. Please try again in the next epoch!

bolt-spammer-helder/src/main.rs

@@ -1,4 +1,4 @@
-use std::{path::PathBuf, str::FromStr};
+use std::str::FromStr;
 
 use alloy::{
     eips::eip2718::Encodable2718,
@@ -37,9 +37,6 @@ struct Opts {
     /// Private key to sign transactions with
     #[clap(short = 'k', long, env)]
     private_key: String,
-    /// Path to the ABI file of the Bolt Registry smart contract
-    #[clap(short = 'a', long, env, default_value = "./registry_abi.json")]
-    registry_abi_path: PathBuf,
     // Flag for generating a blob tx instead of a regular tx
     #[clap(short, long, default_value = "false")]
     blob: bool,