db-sync properties to check

Open
  • Is something wrong?
#701 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
database, testing

Research direction

No file or test entry point is named. Start by locating the repository's DB-sync E2E tests and the code exposing ledger and database balances, then define checks for the listed withdrawal, fixed-total, and pot-consistency properties. Done means these properties are asserted for each relevant test scenario.

Written by the indexing model from the issue text.

Description

db-sync
  • sum withdrawals <= sum rewards (per stake address)
  • total sum of all money in the system is always the same fixed amount.
  • the various pots of money are the same between the ledger state and the DB - reserves, treasury, fees pot, utxo & reward account circulation etc.
Dominant language
Python
Stars
59
Forks
28
Avg merge
13h 57m
Merged PRs (30d)
87

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/cardano-node-tests

All issues in IntersectMBO/cardano-node-tests

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.