Skip to main content

Symbiotic Vault OptIn using kalypso-cli

This guide walks you through the process of requesting a stake from Symbiotic as an operator. Following these steps will help you secure your position within the Kalypso ecosystem and ensure that your operations run smoothly.

📋 Prerequisites​

Before you begin, ensure that you have completed the following:

Symbiotic Operator Registration.​

You would need to register as operator on symbiotic, before requesting delegation from a symbiotic vault. It is recommended to register as operator from symbiotic's web app, otherwise you can use kalypso-cli to register as symbiotic operator.

Symbiotic Operator Registration

If you have already registered as symbiotic operator, you can skip this section and move to Requesting Symbiotic Stake

1. Create .env File​

Start by creating a .env file in the root directory of your project. This file will store the necessary environment variables required for registering the operator on symbiotic.

touch .env

2. Configure Environment Variables​

Open the .env file in your preferred text editor and add the following contents:

PRIVATE_KEY=<<operator_private_key>>
SYMBIOTIC_RPC_URL=<<l1_rpc_url>>
info
env variableNotes/Info
SYMBIOTIC_RPC_URLEthereum Mainnet RPC URL

3. Register with Symbiotic as operator​

With the .env file configured, execute the following command to register operator with symbiotic (if not already done):

./start.sh symbiotic-register

đŸĒ™ Opt Into Vaults​

For request stake/delegation from symbiotic, you must opt into some vault and network (network id for kalypso). Follow these steps to request a stake from Symbiotic:

1. Create .env File​

Start by creating a .env file in the root directory of your project. This file will store the necessary environment variables required for the stake request.

touch .env

ℹī¸ Why: The .env file holds sensitive information and configuration settings needed for the stake request process. Keeping this information in a separate file enhances security and manageability.

2. Configure Environment Variables​

Open the .env file in your preferred text editor and add the following contents:

PRIVATE_KEY=<<operator_private_key>>
SYMBIOTIC_RPC_URL=<<l1_rpc_url>>
VAULT_ADDRESS=<<vault address>>
NETWORK_ADDRESS=<<network address>>
info
env variableNotes/Info
SYMBIOTIC_RPC_URLEthereum Mainnet RPC URL

⚠ī¸ Ensure All Variables Are Declared: Please ensure that you have properly configured the following variables in your .env file:

  • PRIVATE_KEY: Your operator's private key used to sign transactions. Keep this key secure and do not share it.
  • SYMBIOTIC_RPC_URL: The RPC URL of the L1 network provided on which symbiotic is deployed.
  • VAULT_ADDRESS: Vault address you opt in
  • NETWORK_ADDRESS: Network address you opt in
Security Warning

Note: It is strongly advised to visit symbiotic ecosystem and select appropriate vaults and networks you opt in.

Refer for mainnet vault addresses HERE

Once you you have the vault address, add this to you .env

    export VAULT_ADDRESS="vault_address"

3. Opt In​

With the .env file configured, execute the following command to request a stake from Symbiotic:

./start.sh symbiotic-stake

ℹī¸ Why: Running this command initiates the stake request process, sending your operator's credentials to the Symbiotic network. This step is essential to secure your position and enable proof generation within the Kalypso ecosystem.

4. Request Vault Delegation​

For operators to receive delegation from symbiotic, they must ask the vault operator for the delegation along with their address on Telegram channel.

Must inform vault operator

This step is essential. Only after this step vault operator will be know you and send delegation.

📈 Next Steps​

Check whether your operator has received stake using read-stake query. If you don't see any Symbiotic Delegation, reach out on on Telegram channel. Ensure that you have Available Symbiotic Stake little more than the Requirement (Symbiotic)

Once the symbiotic stake request operation is complete, proceed to stake natively to further secure your operations and optimize your participation in the Kalypso network.

ℹī¸ Why: Staking natively enhances your commitment to the network, allowing for better performance, higher reliability, and increased rewards within the ecosystem.

Need Help?

If you encounter any issues or have questions, feel free to reach out to our Telegram channel for assistance.

Next stake natively​