Delegated Staking

Overview

The following steps outline the creation of a staking pool for an already deposited validator node.

Prerequisites

Clone the delegated staking repository or pull the main branch if you have already cloned it.

To deploy and interact with staking contracts via the CLI, use the provided Forge scripts. Follow these steps before proceeding with the deployment:

Install Foundry: Follow the official link for foundry installation.

Install OpenZeppenlin Contracts:

forge install OpenZeppelin/openzeppelin-contracts-upgradeable --no-commit
forge install OpenZeppelin/openzeppelin-contracts --no-commit

Set the RPC URL:

export FOUNDRY_ETH_RPC_URL=http://localhost:4202

Set the Private Key:
```
export PRIVATE_KEY=0x...
```
PRIVATE_KEY refers to the staking pool contract owner's private key.

Step 1: Contract Deployment

Choose one of the variant Non-Liquid/Liquid staking contract to deploy:

Deploying NonLiquidDelegation Contract

forge script script/Deploy.s.sol --broadcast --legacy --sig "nonLiquidDelegation()"

Example output:

  Signer is 0x15fc323DFE5D5DCfbeEdc25CEcbf57f676634d77
  Proxy deployed: 0x7A0b7e6D24eDe78260c9ddBD98e828B0e11A8EA2
  Implementation deployed: 0x7C623e01c5ce2e313C223ef2aEc1Ae5C6d12D9DD
  Owner is 0x15fc323DFE5D5DCfbeEdc25CEcbf57f676634d77
  Upgraded to version: 0.3.4

Alternatively, deploy the LiquidDelegation contract.

Deploying LiquidDelegation Contract

forge script script/Deploy.s.sol --broadcast --legacy --sig "liquidDelegation(string,string)" Name Symbol

where Name and Symbol represent your Liquid Staking Token (LST).

Example output:

  Signer is 0x15fc323DFE5D5DCfbeEdc25CEcbf57f676634d77
  Proxy deployed: 0x7A0b7e6D24eDe78260c9ddBD98e828B0e11A8EA2
  Implementation deployed: 0x7C623e01c5ce2e313C223ef2aEc1Ae5C6d12D9DD
  Owner is 0x15fc323DFE5D5DCfbeEdc25CEcbf57f676634d77
  Upgraded to version: 0.3.4

Step 2: Contract Configuration

Configure the validator’s commission rate (e.g., 10%):

forge script script/Configure.s.sol --broadcast --legacy --sig "commissionRate(address payable, uint16)" <DELEGATION_CONTRACT_PROXY_ADDRESS> 1000

You can find DELEGATION_CONTRACT_PROXY_ADDRESS in the output of deployment step 1.

Expected output:

  Running version: 0.3.4
  Commission rate: 0.0%
  New commission rate: 10.0%

Step 3: Validator Addition

Before your validator node can join the staking pool, you have to execute the following steps:

Set the Control Address:

cast send --legacy --private-key <0x...> \
0x00000000005a494c4445504f53495450524f5859 "setControlAddress(bytes,address)" \
<BLS_PUBLIC_KEY> \
<DELEGATION_CONTRACT_PROXY_ADDRESS>

here --private-key <0x...> refers to the private key previously used to deposit stake for the validator node. Example:

cast send --legacy --private-key 0x... \
0x00000000005a494c4445504f53495450524f5859 "setControlAddress(bytes,address)" \
0x92fbe50544dce63cfdcc88301d7412f0edea024c91ae5d6a04c7cd3819edfc1b9d75d9121080af12e00f054d221f876c \
0x7A0b7e6D24eDe78260c9ddBD98e828B0e11A8EA2

Join the Staking Pool:

cast send --legacy --private-key $PRIVATE_KEY \
<DELEGATION_CONTRACT_PROXY_ADDRESS> "join(bytes,address)" \
<BLS_PUBLIC_KEY> \
<CONTROL_ADDRESS>

Example:

cast send --legacy --private-key $PRIVATE_KEY \
0x7a0b7e6d24ede78260c9ddbd98e828b0e11a8ea2 "join(bytes,address)" \
0x92fbe50544dce63cfdcc88301d7412f0edea024c91ae5d6a04c7cd3819edfc1b9d75d9121080af12e00f054d221f876c \
0xe0c6f3d59b8cda6ce4fd66418212404a63ad8517

The CONTROL_ADDRESS was generated when depositing the minimum stake required of validators. For details, refer to the staking.md.

Step 4: Staking Pool Registration

Once the validator has joined the staking pool, share the with the Zilliqa team to allow users to delegate ZIL to the staking pool on the new staking portal.

Summary

By following these steps, you have successfully deployed, configured, and added a validator into either a Non-Liquid Staking Pool or a Liquid Staking Pool. ZIL holders can now delegate to the pool and you receive commissions on the delegated amount.