Alonzo specific db-sync changes

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

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
Mostly clear
Activity status
Stale
Domain
databases

Research direction

No files, tests, or entry points are named in the issue. Start by locating the db-sync integration and its schema definitions, then determine how execution units and their fee contributions should be represented; done means the requested transaction data supports both listed end-user scenarios.

Written by the indexing model from the issue text.

Description

db-sync

New functionalities/tables:

  • record the number of execution units in each tx
  • record the contribution to the fees of the execution units in the tx

End-user scenarios:

  • how many Plutus scripts had been successfully submitted on a testnet?
  • have the cost of execution per tx for txes with Plutus scripts attached
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.