pocket nodes stake
Stake the node into the network, making it available for service.
Usage:
pocket nodes stake [command]
Available Commands:
custodial Stake a node in the network. Custodial stake uses the same address as operator/output for rewards/return of staked funds.
non-custodial Stake a node in the network, non-custodial stake allows a different output address for rewards/return of staked funds. The signer may be the operator or the output address. The signer must specify the public key of the operator
Use mainline Cosmos SDK best practices to implement non-custodial staking
Deliverables
[ ] Research Morse: Study & understand how non-custodial staking works in Morse
[ ] Research Cosmos: Study & understand what (if any) parts of the Cosmos SDK we should use for non-custodial staking
[ ] Implement: Implement non-custodial staking in Shannon
[ ] CLI: Update the poktrolld to support non-custodial staking
[ ] Test: Add unit, integration and E2E tests
[ ] Tooling: Add Makefile targets to easily trigger (on LocalNet) and test (e2e) non-custodial staking
[ ] Document: Add a new page to dev.poktroll.com explaining how non-custodial staking works and how to use it
[ ] Comments: Add/update TODOs and comments alongside the source code so it is easier to follow.
Non-goals / Non-deliverables
Expanding beyond what Morse has for non-custodial staking for Suppliers
Adding delegation or non-custodial taking for any other actors
Estimated Days of Work
3 days
Disclaimer: This is the total projected number of estimated hours to completion & merge. The owner of this tickets is expected to use this GitHub issue to communicate with the core protocol team along the way, with update & feedback for each deliverable throughout the duration of this work._
Objective
Feature parity with non-custodial staking from Morse.
Origin Document
437
Non-custodial staking command in Morse:
Goals
Deliverables
poktrolldto support non-custodial stakingMakefiletargets to easily trigger (on LocalNet) and test (e2e) non-custodial stakingNon-goals / Non-deliverables
Estimated Days of Work
3 days
Disclaimer: This is the total projected number of estimated hours to completion & merge. The owner of this tickets is expected to use this GitHub issue to communicate with the core protocol team along the way, with update & feedback for each deliverable throughout the duration of this work._
Creator: @Olshansk Co-Owners: @moatus