Skip to content

local-dev.md

Latest commit

 

History

History
60 lines (38 loc) · 2.17 KB

local-dev.md

File metadata and controls

60 lines (38 loc) · 2.17 KB
Raw

SSV Network

Intro | Architecture | Setup | Tasks | Local development | Roles | Operator owners

Specification | Flows | Mainnet upgrade playbook | Deployments

Local development

This repository supports both fresh local deployments and fork-based validation of real environment configs.

Fresh local deployment

Use the local deployment config and deploy everything from scratch:

just deploy-fresh local

This is the quickest way to get a complete local protocol instance with the v2 module set.

Fork-based upgrade validation

The preferred way to validate an environment upgrade is to run it on a local fork and then execute the strict fork tests.

Example:

anvil --fork-url "$HOODI_RPC_URL" --port 8545
just upgrade-test-fork hoodi-stage

Other useful variants:

just upgrade-fork hoodi-stage
just test-fork hoodi-stage
just smoke-test hoodi-stage

Environment sources of truth

  • deployments/<env>/config.json defines the intended configuration for that environment
  • deployments/<env>/deploy-result*.json stores deployment outputs
  • deployments/<env>/upgrade-result*.json stores upgrade outputs

For the detailed schema and expected artifacts, use deployments/README.md.

Verification and explorer flows

This repo keeps explorer verification and post-upgrade config verification as script-driven workflows rather than documenting long manual steps here.

Use:

Troubleshooting

  • If an env-driven command fails early, check that .env has the required RPC URL and signer key for that environment.
  • If fork tests cannot find deployed state, confirm Anvil is running on 127.0.0.1:8545 and that the chosen env config matches the forked network.
  • If verification output looks stale, rerun the relevant deploy or upgrade flow so the latest result artifact is regenerated.