Skip to main content
For a complete list of contract addresses used in this guide, see the Contract Addresses page.

​
1. Register as EigenLayer Operator

Before you register into Taiyi protocol, you need to register as an EigenLayer operator first. Please follow the EigenLayer Operator Registration Guide to register as an EigenLayer operator.

​
2. Register as Taiyi Validator AVS Operator

After register as an EigenLayer operator, register yourself into the Taiyi protocol as an Taiyi Validator AVS Operator. This step establishes your operator identity in the taiyi validator avs protocol.
EigenLayer Core Contracts showing Operator registration through Delegation Manager
Source: EigenLayer AVS Book - Operators 
taiyi-cli register-for-operator-sets \
    --execution-rpc-url $EXECUTION_URL \
    --operator-set-ids 0 \
    --operator-bls-key $UNDERWRITER_BLS_PUBLIC_KEY \
    --private-key $UNDERWRITER_ECDSA_PRIVATE_KEY \
    --allocation-manager-address 0x78469728304326CBc65f8f95FA756B0B73164462 \
    --avs-address 0xC568b4cB806f38a5c487DE63F5C4dD600d53767E \
    --avs-directory-address 0x055733000064333CaDDbC92763c58BF0192fFeBf \
    --salt 0x0000000000000000000000000000000000000000000000000000000000000000 \
    --socket $YOUR_ORGS_NAME
This command:
  1. Creates a registration signature with the AVS Directory
  2. Registers your operator address with Taiyi AVS
  3. Links your stake to the Taiyi service

​
3. Register Validators

After registering as an Operator, you can register your validator keys to the Taiyi service. This allows your validator to participate in the preconf game. 
taiyi-cli register-validators \
    --execution-rpc-url $EXECUTION_URL \
    --private-key $VALIDATOR_OPERATOR_PRIVATE_KEY \
    --taiyi-middleware-address 0xC568b4cB806f38a5c487DE63F5C4dD600d53767E \
    --operator-address $VALIDATOR_OPERATOR_ADDRESS \
    --collateral 100000000000000000 \
    local-keystore \
    --path /path/to/validators \
    --password-path /path/to/secrets
The validator pubkeys should be your testnet validator’s pubkey.If you have your validators already staking in network, you can use the existing validator keys to register with pod-owners 0x0000000000000000000000000000000000000000.If you have your validators already natively staking in eigenlayer, you can use the existing validator keys to register with your own eigenlayer pod address.We don’t support register as gateway avs operator right now,so make sure to delegated your preconf rights to luban testnet gateway pubkey: b2796db1455143b39c4b6104dddbaf3fdca059009b9df3f61c729bac81cadd355fcc3fc61f5185a4748eb3bf298c0ad9

​
4. Delegate Validator Keys

Finally, delegate your validator keys to the Taiyi Gateway. This allows your validator to participate in the network.
Preconfirmation API Flow showing delegation and constraint management
Source: Preconfirmations API Specification 
taiyi-cli delegate \
  --relay-url https://relay.holesky.luban.wtf \
  --underwriter-pubkey b2796db1455143b39c4b6104dddbaf3fdca059009b9df3f61c729bac81cadd355fcc3fc61f5185a4748eb3bf298c0ad9 \
  --network holesky \
  local-keystore \
  --path /path/to/validators \
  --password-path /path/to/secrets
For additional key source options and detailed usage of the delegate command, see the Taiyi CLI Delegate Command documentation.
This step follows the /constraints/v0/builder/delegate endpoint specification from the Preconfirmations API to perform the underwriter delegation. The process involves:
  1. Proposer (your validator) electing the Underwriter through delegation
  2. Underwriter managing preconfirmation constraints
  3. Relay coordinating between proposer, underwriter, and builder
  4. Builder receiving constraints and submitting compliant blocks

​
4. Verification

Verify whether your operator is registered in the Taiyi Validator AVS protocol:
  1. Check your stake:
taiyi-cli operator-info \
    --execution-rpc-url <EXECUTION_URL> \
    --operator-address <VALIDATOR_OPERATOR_ADDRESS> \
    --linglong-coordinator-address 0x4778517B371D996476D0a0Fc240fa754391ad5e7

​
5. Deposit WETH to EigenLayer Strategy(Optional)

Before depositing into the EigenLayer strategy contract, ensure you have sufficient WETH tokens in your account. You can check your WETH balance on testnet at Etherscan. If you already stake in eigenlayer, you can skip this step. To check your balance:
  1. Go to the WETH contract on Etherscan
  2. Navigate to the “Read Contract” tab
  3. Find the balanceOf function
  4. Enter your wallet address
  5. Click “Query” to see your balance
If you need to acquire WETH:
  1. First obtain some Holesky ETH from a faucet
  2. Convert your ETH to WETH by interacting with the WETH contract
First, you need to deposit WETH into the EigenLayer strategy contract. This stake serves as collateral for your node’s operations.
EigenLayer Core Contracts showing Strategy Manager receiving deposits from Stakers
Source: EigenLayer AVS Book - Stakers 
# Convert ETH to WETH first if needed
# Then approve and deposit WETH to allocation manager
# allocation manager address modify distribution
taiyi-cli deposit \
  --execution-rpc-url https://ethereum-holesky.publicnode.com \
  --strategy-address 0x80528D6e9A2BAbFc766965E0E26d5aB08D9CFaF9 \
  --amount <AMOUNT> \
  --private-key <YOUR_PRIVATE_KEY> \
  --strategy-manager-address 0xdfB5f6CE42aAA7830E94ECFCcAd411beF4d4D5b6 \
  --allocation-manager-address 0x78469728304326CBc65f8f95FA756B0B73164462 \
  --operator-set-id 0 \
  --linglong-eigenlayer-middleware-address 0xC568b4cB806f38a5c487DE63F5C4dD600d53767E \
  --wad 1000000000000000000
This command:
  1. Approves the Strategy Manager to spend your WETH
  2. Deposits WETH into the EigenLayer strategy
  3. Records your stake in the protocol
⌘I