Other Useful Operations
This section covers additional operations that are essential for managing your role as a Hardware Operator. These operations allow you to maintain control over assigned requests and ensure the smooth functioning of your operations within the Kalypso ecosystem.
$ Read Stake
Use the Read Stake Operation to check the overall stake
1. Create .env File
Begin by creating a .env file in the root directory of your project.
touch .env
2. Configure Environment Variables
Open the .env file in your preferred text editor and add the following contents:
OPERATOR_ADDRESS=<<your_operator_address>>
./start.sh read-stake
Above command will print the stake details and task assignments requirments for a give operator address
Operators need to have one of the tokens in the Native section and any one of the tokens in the Symbiotic section to get a job.
Requirement Type | Token | Amount
---------------------+--------------------------------------------+---------------------
Native | 0xb5570d4d39dd20f61def7c0d6846790360b89a18 | 1000000000000000000
| |
----------- | (and one of the token requirement below) | -----------
| |
Symbiotic | 0x854493fb9f844c8632140fff9b66207b10027e8d | 2000000000000000000
Symbiotic | 0x5e478cb7576906fe2a443684adcd9a0dfc547abd | 6000000000000000000
Symbiotic | 0xb5570d4d39dd20f61def7c0d6846790360b89a18 | 2000000000000000000
Explanation of Each Field
- Requirement Type: Staking Module in which operator should have stake. There are two currently Native and Symbiotic
- Token: Address of the token which must be delegated to operator
- Amount: Amount of the token which must be delegated operator
Tokens Delegated to operator <<your operator address>>
Stake Category | Token | Amount
-------------------------------+--------------------------------------------+---------------------
Total Native Stake | 0xb5570d4d39dd20f61def7c0d6846790360b89a18 | 288747244684092484678
Total Native Stake Locked | 0xb5570d4d39dd20f61def7c0d6846790360b89a18 | 9000000000000000000
Available Native Stake | 0xb5570d4d39dd20f61def7c0d6846790360b89a18 | 279747244684092484678
------- | ------- | -------
Total Symbiotic Stake | 0x5e478cb7576906fe2a443684adcd9a0dfc547abd | 13961720430107528912270
Total Symbiotic Stake Locked | 0x5e478cb7576906fe2a443684adcd9a0dfc547abd | 6000000000000000000
Available Symbiotic Stake | 0x5e478cb7576906fe2a443684adcd9a0dfc547abd | 13955720430107528912270
Operation 'Read Stake Data' completed successfully.
Bootstrap completed successfully.
Explanation of Each Field
- Total Native Stake: Total Number of Native Stake Tokens the operator has staked in the Native staking module
- Total Native Stake Locked: Total Number of Native Stake Tokens locked. This is 0 (or) column is empty when there are no tasks assigned at time of query
- Total Symbiotic Stake: Total Number of Symbiotic Tokens the operator has received as delegation from the vault.
- Total Symbiotic Stake Locked: Total Number of Symbiotic Tokens locked for the operator.
- Available Native Stake: Number Native Stake Tokens available/free. For operator to receive task, ensure that
Available Native Stake > Requirement Type (Native) - Available Symbiotic Stake: Number Symbiotic Stake Tokens available/free. For operator to receive task, ensure that
Available Symbiotic Stake > Requirement Type (Symbiotic)
For jobs to be successfully assigned, operator must have Available Symbiotic Stake for atleast one token corresponding in Requirement Type Section
🗑️ Discard Request
Use the Discard Request option to remove an already assigned request. Caution: This operation will result in slashing, meaning a penalty will be applied to your staked tokens. Use this feature judiciously to maintain your reputation and staking balance within the network.
⚠️ Warning: Discarding a request should be performed only when absolutely necessary, as it incurs a slashing penalty. Frequent or unjustified discards can negatively impact your standing in the network.
📋 Prerequisites
Before performing the Discard Request operation, ensure that you have received an active request assigned to you. You can only Discard Request assigned to you.
🛠️ Steps to Discard a Request
Follow these steps to discard an assigned request:
1. Create .env File
Begin by creating a .env file in the root directory of your project. This file will store the necessary environment variables required for discarding a request.
touch .env
ℹ️ Why: The .env file holds sensitive information and configuration settings needed for the discard 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=<<your_operator_private_key>>
RPC_URL=<<l2_rpc_url>>
ASK_ID=<<request_id_to_discard>>
- PRIVATE_KEY: Your operator's private key used to sign transactions. Keep this key secure and do not share it.
- RPC_URL: The RPC URL of the L2 Blockchain.
- ASK_ID: The unique identifier of the request you intend to discard.
⚠️ Ensure All Variables Are Declared:
Please ensure that you have properly configured the following variables in your .env file:
Warning: Exposing your private key can lead to unauthorized access and potential loss of funds. Ensure that the .env file is stored securely and is not exposed publicly or committed to version control systems.
ℹ️ Why: Proper configuration of environment variables is crucial for securely interacting with the Kalypso network. These variables ensure that your discard request is authenticated and routed correctly.
3. Request to Discard the Assigned Request
With the .env file configured, execute the following command to discard the assigned request:
./start.sh discard-request
ℹ️ Why: Running this command initiates the discard process, sending your operator's credentials and the specific request ID to the Kalypso network. This step is essential to remove the assigned request from your queue, especially in scenarios where the request cannot be fulfilled.
📈 Post-Discard Actions
After successfully discarding a request, consider the following actions:
- Monitor Your Staking Balance: Ensure that the slashing penalty has been appropriately applied to your staked tokens.
- Review Assigned Requests: Regularly check your assigned requests to manage your workload effectively and minimize the need for discards.
Request to Leave the Marketplace
To request leaving the marketplace, use the following command:
If you do not have any active requests, you will exit the marketplace immediately. If you have active requests, the system will stop accepting new requests, and you will need to execute leave-marketplace as described in the next step after completing the active requests.
./start.sh request-marketplace-exit
Leave the Marketplace
To leave the marketplace, run the following command:
./start.sh leave-marketplace
Change Proof Generation Cost/ Proving Time/ Operator commission
Changing the proving cost, proving time or operator commission is a multi-step process as it involves altering the commitments prover has made to the network. It involves first exiting the market and then rejoining with different params .
If the operator already has a job assigned, they must first request to leave the market and then leave the marketplace. Otherwise, they can directly call leave marketplace.
Note: This operation can be safely performed without closing the prover in the background.
Open the .env file in your preferred text editor and edit the following content:
PROOF_GENERATION_COST=1000000 # Edit this value, (1000000 here means 1 USDC)
OPERATOR_COMMISSION=1000000000000000000 # max 1e18 (1e18 means 100%)
PROPOSED_TIME=1200 #this number is in seconds
Operators must chose PROPOSED_TIME wisely. Too small a number may cause jobs being missed. Too large a number could decrease the selection probability
Then, join the market again using:
./start.sh register-join
For more details, refer here.
If you encounter any issues or have questions, feel free to reach out to our Telegram channel for assistance.