Wallet Signatures
Last updated
Last updated
There are three different wallet options that are available to node operators of Koii who want to be able to sign transactions, store, stake, send and receive Koii Tokens on K2. The three wallet options are:
As suggested by the name, this is a node operator's main wallet; it is responsible for funding the other wallets with KOII tokens and its signature key is necessary to pay transaction fees in a Koii Task.
The primary purpose of this wallet is to stake on Koii tasks. Node operators who wish to run a particular task have to create a staking wallet and fund the staking wallet with their main wallet; tokens in the staking wallet can in turn be used to stake on a Koii task.
The distribution wallet is required if a node needs to submit a distribution list to K2. The node creates and funds the distribution wallet from the main wallet so there can be a rent exemption.
Yes! as you probably already guessed, the Namespace wrapper offers a method that injects the main system wallet as the first signer for making transaction fees payments. The sendAndConfirmTransactionWrapper
method is in charge of this.
This might seem a bit odd - why would a Koii node allow a task to use it's wallet? Well, in many cases, a task will need to write records to a blockchain, or to K2 directly (all tasks do this to manage flows). Some examples might include bridging, minting NFTs, or other on-chain asset management.
In these cases, the task operator can opt into allowing their wallet to be used by a task directly, in exchange for a greater reward. Most tasks of this nature must follow the , ensuring that the code is properly audited before a task is promoted to the community.
The sendAndConfirmTransactionWrapper
takes in two parameters:
transaction
: Endpoint path to append to namespace
singers
: Other wallets signatures
Example: