IntersectMBO / IntersectMBO/cardano-node

[FEATURE] - query each stake snapshot independently [Draft]

Open
#4,982 34 comments 3 reactions 0 assignees View on GitHub
comp: cardano-cli type: feature request user type: internal
Dominant language
Haskell
Stars
3.2k
Forks
754
Avg merge
4d 20h
Merged PRs (30d)
20

Description

## What
A command to query each stake snaphost independently; for example

`cardano-cli query stake-snapshot --mark-snapshot ... `
`cardano-cli query stake-snapshot --go-snapshot ...`

the output should contain all 3 maps

[
"delegations",
"poolParams",
"stake"
]

## Why

Currently, many tools rely on dumping the entire ledger-state to then extract the required snapshot values which is expensive and inefficient and there is no alternative good solution yet.

## Personas

- [ ] SPOs
- [ ] dApp Devs
- [ ] Exchanges
- [x] Wallets
- [x] 3rd party tools
- [ ] ADA holders

## Definition of Done (DoD)

- [ ] [Acceptance Criteria + User Stories & DoD](https://input-output.atlassian.net/wiki/spaces/QA/pages/3584229468/Acceptance+Criteria+DoD) created and singed-off (by PO, dev & test owners)
- [ ] Builds successfully on CI
- [ ] Code & Test review (as per Acceptance Criteria)
- [ ] There is documentation and/or examples for the new functionality (usage/response)
- [ ] Log/record changes on **Vnext** (or similar depending on what we adopt)
- [ ] Ticket number(s) included in PR description
- [ ] All Acceptance Criteria met and covered by dev/unit/property/integration tests
- [ ] System/E2E automated tests + System Test Engineer Owner Sign-off

> **_NOTE:_** Ideally, we should merge only fully implemented and tested features into the master branch.
> So all the above steps are required for the PR to be merged.
> In order to avoid the PRs becoming stale and requiring to be rebased on master, these can be merged
> after a reasonable time (current agreement is 3 days) if the System Test Engineer Owner's sign-off
> was not provided (last step in the DoD).

> **_IMPORTANT:_** Any deviation from the plan should be discussed and agreed as a comment in the Feature file.

## Sign-off

- [ ] Product Owner
- [ ] Dev Owner
- [ ] System Test Engineer Owner

# Related PRs

1. PR # here

## Acceptance Criteria

Acceptance Criteria & User Stories define here (or in a separate file (linked here) for a big feature)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.