🕹️Validator Management

Operators in MultichainZ Liquid Staking will be responsible for validator key generation and activating the keys by depositing 32 ETH held in our pools into the beacon chain.

Validator Registration Process for Liquid Staking Operators

This documentation is intended for operators within the Multichainz Liquid Staking ecosystem. It outlines the steps necessary to register a validator on the network, which is a critical process for expanding the staking capacity and ensuring the robustness of the decentralized staking platform.

Overview

Validators are crucial to the proof of stake (PoS) consensus mechanism. As an operator, registering a validator involves staking Ethereum in return for new validators, which are then responsible for validating transactions and maintaining the security and integrity of the blockchain.

Requirements

Before initiating the validator registration process, ensure that you have:

1. Sufficient Funds: At least 32 ETH per validator is required for staking.

2. Operator ID: You must be a trusted operator within the Multichainz network. This is verified through the Node Operators Registry.

3. Withdrawal Credentials: These are critical for setting up the validator's ability to withdraw staked ETH in the future.

Always make sure the Withdrawal_Address set in the staking-deposit-CLI corresponds to the protocol's own consensus Layer vault address to avoid a mismatch in the signature data during deposit.

Steps to Register a Validator

1. Prepare Validator Data

You need to prepare the following data for each validator you wish to register:

• Public Key: The public key associated with the validator.

• Signature: A signature proving the ownership of the public key.

• Deposit Data Root: This is a hash of the validator's credentials and is used to verify the data integrity during the registration process.

2. Stake ETH to the Beacon Chain

To register a validator, you must stake ETH. This involves sending ETH to the Ethereum 2.0 deposit contract through the Liquid Staking contract. This action will also mint a corresponding Validator NFT (vNFT), representing your validator on the network.

3. Execute the Registration Transaction

Using the registerValidator function, you will submit the prepared data to the network. This function takes arrays of public keys, signatures, and deposit data roots as inputs. Here is the function signature for clarity:

function registerValidator(
    bytes[] calldata _pubkeys,
    bytes[] calldata _signatures,
    bytes32[] calldata _depositDataRoots
)

Make sure that the arrays are well-formed and that each index corresponds across public keys, signatures, and deposit data roots to avoid transaction reversion.

4. Verify Transaction Success

After submitting the transaction, verify that it has successfully executed. This can typically be done by checking for events emitted by the contract such as ValidatorRegistered.

Monitoring the Ethereum 2.0 deposit contract for a successful deposit can also confirm that the registration process has completed.

Handling Errors

Be prepared to handle potential errors that may arise during the registration process:

• Insufficient Funds: Ensure each operator controller address has enough ETH to cover the deposit.

• Trust Verification: The system will verify if the operator is trusted; untrusted operators cannot register validators.

• Data Mismatch: Errors in the public key, signature, or deposit data root can cause the transaction to fail.

For further assistance or more detailed technical guidance, please contact technical support.