Description
What
stake-address-info to output pool-id and drep-id in both hex and bech32.
Why
This way it is easier for users to use this information in tools that only support one format or another.
This may require waiting for either CIP105 or CIP129 to be approved. The problematic part is DRepID for script based DReps.
Personas
- SPOs
- dApp Devs
- Exchanges
- Wallets
- 3rd party tools
- ADA holders
Definition of Done (DoD)
- Acceptance Criteria + User Stories & 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
- PR # here
Acceptance Criteria
When I query the stake-address-info, the delegation choices for DReps and Pools are displayed in both hex and bech32 format.