📄️ Commit Modules
Commit-Boost provides an open platform for developers to create and distribute commitment protocol sidecars. Commit Modules are the primary way to add custom logic: they run as sidecar processes alongside the PBS and Signer services, and can request signatures from the proposer.
📄️ Requesting proposer commitment signatures with Commit-Boost
When you create a new validator on the Ethereum network, one of the steps is the generation of a new BLS private key (commonly known as the "validator key" or the "signer key") and its corresponding BLS public key (the "validator pubkey", used as an identifier). Typically this private key will be used by an Ethereum consensus client to sign things such as attestations and blocks for publication on the Beacon chain. These signatures prove that you, as the owner of that private key, approve of the data being signed. However, as general-purpose private keys, they can also be used to sign other arbitrary messages not destined for the Beacon chain.
📄️ Extending PBS
The PBS binary that ships with Commit-Boost can be extended with custom logic. This is not a config-level module declaration like commit modules: you replace the PBS binary entirely by implementing the BuilderApi trait (the default implementation is the DefaultBuilderApi struct). For system context on how the PBS service fits into the Commit-Boost architecture, see the Architecture Overview.
📄️ Environment setup
Dirk signer