feat: add README for Evolve Network Module (beta)

Author: randygrok

attester/README.md

@@ -5,6 +5,7 @@
 This command-line helper joins the attester set of an Evolve-based chain and streams attestations for new blocks. It is the first public beta of the attester workflow and intentionally omits a number of production-hardening features (automatic key management, batching, robust persistence, etc.). The goal is to unblock experimentation on top of the upcoming attester mode.
 
 ## What it does
+
 - Configures the Cosmos SDK Bech32 prefixes required by the target chain.
 - Derives an operator account key from a mnemonic and loads the validator consensus key from the local `priv_validator_key.json`.
 - Submits a `MsgJoinAttesterSet` transaction so the validator's consensus key is registered as an attester.
@@ -13,12 +14,14 @@ This command-line helper joins the attester set of an Evolve-based chain and str
 - Retries failed submissions a few times and keeps catching up when the attester falls behind.
 
 ## Prerequisites
+
 - An Evolve node exposing RPC on `tcp://HOST:PORT` and REST API on `http://HOST:PORT`.
 - Access to the validator home directory so the attester can read `config/priv_validator_key.json` and `data/priv_validator_state.json`.
 - A funded Cosmos SDK account mnemonic that will cover the attestation fees.
 - The chain ID and Bech32 prefixes used by your deployment.
 
 ## Running the attester
+
 Build with Go 1.22+:
 
 ```bash
@@ -39,18 +42,21 @@ Run it against your node (adjust the sample values):
 ```
 
 ### Important flags
+
 - `--home` – validator home directory containing the CometBFT private validator files.
 - `--mnemonic` – Cosmos SDK mnemonic for the operator account that pays fees.
 - `--bech32-account-prefix` and friends – override if your chain does not use the defaults (`gm`, `gmvaloper`, etc.).
 - `--node` / `--api-addr` – RPC and REST endpoints used for account queries and block data.
 
 ## Operational notes
+
 - The attester assumes the node accepts `MsgAttest` at every height. Current networks only process attestations at checkpoint heights (multiples of the epoch length); out-of-window submissions will be rejected with code 18 (`invalid request`).
 - Sequence numbers are cached in memory. Restarting the process while transactions are pending can still produce sequence mismatches.
 - HTTP polling currently drives block detection. There is no WebSocket subscription or backoff logic yet, so running it against remote nodes may require proxying/caching to avoid throttling.
 - Logging is verbose by default to aid debugging. Remove `--verbose` once the setup is stable.
 
 ## Limitations and future work
+
 - No automatic key rotation or secure storage – mnemonic and consensus keys must be provided manually.
 - No persistence of attestation state across restarts beyond what the chain tracks.
 - Lacks production monitoring hooks, metrics, and alerting.