Custom db-sync checks

Open
  • Is something wrong?
#1,099 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
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
databases, testing

Research direction

No files, tests, or entry points are named. Start by locating the existing db-sync checks in the cardano-node-tests repository and determine how epoch metrics and transaction fees are currently queried. Done means checks cover rewards, recipient addresses, circulating supply, transaction-type fees, treasury, and reserves per epoch.

Written by the indexing model from the issue text.

Description

db-sync
  • total rewards generated per epoch
  • total addresses receiving rewards per epoch
  • total circulating supply
  • tx fees for different transaction types
  • treasury and reserves values per epoch
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.