Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Staking support in cardano-cli #139

Closed
deepfire opened this issue Aug 22, 2019 · 2 comments
Closed

Staking support in cardano-cli #139

deepfire opened this issue Aug 22, 2019 · 2 comments
Assignees
Labels
cli revision is used to group all the Node CLI tickets priority medium issues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesn shelley testnet issues/PRs that need to be done for the Shelley testnet

Comments

@deepfire
Copy link
Contributor

deepfire commented Aug 22, 2019

We need to support staking-related scenarios in CLI tooling, as per Chapter 4 of https://hydra.iohk.io/build/902246/download/1/delegation_design_spec.pdf

This is part of #30

The staking scenarios

  1. Stake Pool Registration:
    • manipulation of pool metadata and stake pool registration certificate.
    • submission to the blockchain
    • status queries
  2. Querying of the active stake pools (and of their metadata).
  3. Delegation support:
    • staking key registration and delegation certificate manipulation
    • submission
    • querying the delegation status
  4. Individual staking, which seems to be a variation of the above procedures.

Implementation

Continuing with the established trend, cardano-node will be acting as a validator and the block chain agent, whereas the cardano-cli will deal with forming of the data blobs and generally the UI for the above operations.

The communication between cardano-node and cardano-cli is expected to be at least partly formulated in terms of generalised transactions, but with extensions, since the extended metadata queries, such as for state of pool/staking key/delegation.

An important parallel development is a sister update system node-to-client protocol, which is expected to share a similar structure (generalised transactions + extended status queries).

Dependencies

  1. We need proper generalised transaction support for transactions beyond just UTxO expenditures. This is being worked on in Merge update-confirmation and adoption thresholds cardano-ledger#623
@CodiePP CodiePP added this to Backlog in ActiveBoard Oct 16, 2019
@Jimbo4350 Jimbo4350 added priority medium issues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesn shelley testnet issues/PRs that need to be done for the Shelley testnet labels Jan 14, 2020
@kevinhammond
Copy link
Contributor

In train for Shelley

@Jimbo4350
Copy link
Contributor

Closing as we are currently redefining scope.

ActiveBoard automation moved this from Backlog to Done May 26, 2020
CLI Revision automation moved this from To do to Done May 26, 2020
@vhulchenko-iohk vhulchenko-iohk added the cli revision is used to group all the Node CLI tickets label May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli revision is used to group all the Node CLI tickets priority medium issues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesn shelley testnet issues/PRs that need to be done for the Shelley testnet
Projects
No open projects
ActiveBoard
  
Done
CLI Revision
  
Done
Development

No branches or pull requests

5 participants