Use Web3Signer to override the suggested fee recipient for K2 validator payout fund splitter smart contracts and more
Requires mevPlus version 0.2.0+In this tutorial, we’ll guide you through the process of setting up Native Delegation using Web3Signer for designating a single K2 payout recipient and representative wallet in the context of the K2 protocol. This works regardless of your validator configurations on your node.
MEV Plus
, you need to pass multiple comma-seperated private keys to the k2.eth1-private-key
flag. 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.
NOTE: Each validator/group of validators that have a unique fee recipient needs a representative wallet set up. I.e 1 representative wallet for 1 fee recipient for payout management.
For node operators running multiple validators of which each have unique fee recipients, one has the option to set a master fee recipient and a single representative address to register and manage all these validators.
<keystore_passwords_dir_path>
with the path to a directory that contains only text files of the keystore passwords to each of your validators.<keystores_dir_path>
with the path to your directory that contains your validator keystore files.<eth_network>
with the network to which you are running your node and softwares for i.e mainnet
, holesky
, etc.-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.
<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:
Web3Signer
to manage master payouts within the K2 protocol. This approach streamlines the process of managing multiple validators with multiple unique fee recipients on the node while ensuring rewards are directed to the desired payout address.