Practical overview
When it fits
Use Sedge when you want a command-line workflow to configure and run an on-premise proof-of-stake node setup, with validator key steps included when needed.
Who it is for
- Blockchain node operators setting up proof-of-stake infrastructure.
- Validator operators who need a CLI workflow for generating or importing keystores alongside node configuration.
Documented uses
- Generate Docker Compose and `.env` files for a chosen client configuration.
- Generate validator keystores or import existing keys.
- Check Docker-related dependencies and execute a configured node stack.
Requirements & limits
The project is publicly available on GitHub under the Apache-2.0 license. Listed installation routes are a release binary, Homebrew, Go, or building from source.
- Docker and the Docker Compose plugin are dependencies.
- The default execution runs execution and consensus nodes; validator execution begins after consensus sync.
- Sedge’s documented workflow includes both interactive and customizable non-interactive modes.
- The repository identifies the setup as on-premise and notes validator key security as an operator responsibility.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Use the interactive CLI setup workflow
Generate and run a configured node and validator setup through Sedge’s documented interactive workflow.
Before you start
- Sedge installed using one of its listed installation methods.
- Docker and the Docker Compose plugin; Sedge can provide installation instructions or install them if absent.
Steps
Start the interactive workflow with
sedge cli.Generate the Docker Compose file and
.envfile for the selected client configuration.Generate a validator keystore or import one, then check dependencies as prompted.
Execute the generated Compose file; execution and consensus nodes run by default, and the validator client starts after consensus syncs.
Expected outcome
A generated and executed node setup, with validator execution following consensus-node synchronization when a validator is configured.
Guide limitations
- The README describes this as an on-premise full-node setup.
- The validator client does not start until the consensus node is synced.
- The repository cautions users to verify downloaded binaries come from a reputable source.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- NethermindEth/sedge · Official homepage title · retained in its source language

