Requires MEV Plus version 0.2.0+ installed with K2 native module of version 0.5.0+In this tutorial, we’ll guide you through Rocketpool Native Delegation using Web3Signer - 100% compatible with your Rocketpool smart node. Web3Signer will allow the node operator withdrawal address to be specified for K2 payouts. The K2 payout address can be later updated if the protocol exposes a smoothening pool for example.
k2.eth1-private-key
flag of the MEV Plus configuration for each representative that will serve each payout address. This ensures there is a representative wallet available and configured for each payout (fee recipient) group of validators so that a K2 fee recipient can be registered.
<keystore_passwords_dir_path>
with the path to a directory that contains only text files of the keystore passwords to each of your validators.
Replace the <keystores_dir_path>
with the path to your directory that contains your validator keystore files.
Replace the <eth_network>
with the network to which you are running your node and softwares for i.e mainnet
, holesky
, etc.
The K2 Native Delegation module only uses Web3Signer to sign registration messages and not any other payload. It does not put any validator at risk of slashing through the module.
Ensure the password text files’ filenames are EXACTLY the same filenames as its corresponding keystore file it unlocks.
-k2.web3-signer-url
flag to the URL of your running Web3Signer instance.
Additionally, set the -k2.payout-recipient
flag to the desired payout recipient address i.e. the node runner withdrawal address for the Rocketpool Protocol.
<web3signer_url>
with the address thatWeb3Signer is running on, and set the <payout_recipient_address>
to the designated ECDSA address that all rewards should be paid out to.
Additional advanced configurations for proposer and K2 registration are available here.
Save the system file for MEV Plus and reload systemctl to pick up the new service file: