Guide for Block Keeper testing on Shellnet
Test joining the protocol
Last updated
Test joining the protocol
Last updated
1. Obtaining the License Owner's Key Pair
Go to the .
Follow the instructions in the to obtain the License Owner's key pair.
2. Gaining Access to the User's License Contracts
The License Owner should send their public key
to a GOSH representative via .
The GOSH team will deploy licenses and provide you with the their addresses and unique on-chain numbers.
5. Deploying a Block Keeper Wallet with a Whitelist
Before deploying a BK Wallet all the delegating licenses have to be deployed, and their on-chain unique numbers have to be collected. They will be placed into the wallet's whitelist during deployment.
To deploy the BK wallet, follow the instructions in the .
As a result, you will get something like the following:
Save your BK wallet address, Node ID
, and the file containing the BK Node Owner keys — these will be needed to run the staking script.
5. Delegating a License to a BK Wallet
A maximum of 5 licenses can be delegated to a single node.
Where:
pubkey
- the BK Node Owner's pubkey.
Example of calling the method:
You can check the delegation status by calling the getBK()
method in the License contract.
Example command:
The method will return the BK wallet address to which the license has been delegated:
or null
if no delegation has occurred:
You can obtain the on-chain unique number of the License by calling the getDetails()
method in the License contract:
result:
6. Staking
To initiate staking, at least one license must be delegated to the node.
To delegate a license, a License Owner should call the addBKWallet(uint256 pubkey)
method in a in each License contract.
Learn more about .
Only after completing all previous steps can the Node Owner run the .