Automate Conway update deposit scenario
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- testing-qa
Research direction
No files, tests, or entry points are named. First confirm with maintainers which deposit value should apply in each Shelley and Conway scenario, then identify the existing stake/deposit test entry point and define passing assertions for the automated cases.
Written by the indexing model from the issue text.
Description
- Shelley era: the user registered a stake key and paid the deposit. Let's assume it was configured in the protocol params to 2 ADA.
- Network upgrades to Conway era.
- A governance action updates the protocol parameters key deposit to 3 ADA
- Conway era: the user deregisters the stake key
a. Shelley Deregistration certificate: should the user use 2ADA or 3ADA deposit return when computing the change?
b. Conway Deregistration certificate: should the user configure deposit value to 2ADA or 3ADA?
The problem could also be simplified to a pre-conway scenario:
- User registers stake key (2 ADA key deposit )
- Protocol parameters are updated -> 3 ADA key deposit.
- User deregisters stake key -> does the user get 2ADA or 3ADA back?
- Dominant language
- Python
- Stars
- 59
- Forks
- 28
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 87
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IntersectMBO/cardano-node-tests
-
node upstream bug
Difficulty 5/5 Over a week Newbie friendliness 25/100
IntersectMBO/cardano-node-tests#3670 · 1 comment ·
Maintainers usually reply within 1 day
-
node upstream bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
IntersectMBO/cardano-node-tests#3669 ·
Maintainers usually reply within 1 day
-
Integrate Antithesis using MOOG into Cardano node test suiteMay be free again @saratomaz claimed this 283 days ago, and no pull request is open. Openenhancement
IntersectMBO/cardano-node-tests#3316 · 1 assignee ·
Maintainers usually reply within 1 day
-
db-sync enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
IntersectMBO/cardano-node-tests#2653 · 1 comment ·
Maintainers usually reply within 1 day
-
[FR] cardano-db-sync - Create tests for new db-sync configurationPossibly taken @ArturWieczorek claimed this 122 days ago. Opendb-sync enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
IntersectMBO/cardano-node-tests#2652 ·
Maintainers usually reply within 1 day
All issues in IntersectMBO/cardano-node-tests
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
deepchem/deepchem#5289 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
UKGovernmentBEIS/inspect_evals#2892 · 1 comment ·
Maintainers usually reply within 1 day
-
Versioning docs: say that no output from the 0.46 warning check means nothing is affectedPossibly taken @grelinfo claimed this today. Opendocumentation priority:low size:S
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
alphacrack/readme2demo#293 ·