hiero-ledger / hiero-ledger/hiero-consensus-node
Transaction tracker
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 407
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
Create a component that tracks which transactions were submitted vs which were handled, to detect lost or missing transactions.
Each transaction has an incrementing ID. The tracker records submitted IDs and handled IDs, then reports discrepancies (gaps, missing transactions, transactions handled by some nodes but not others).
During the benchmark execution we need to identify the occurrences of lost transactions for marking the benchmark's results as valid or invalid
Each node will have its own instance. It should allow to print a report of the situation. We might invoke the report with a command to the node.
Contributor 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.
Research direction
No files, tests, or command entry points are named. Start by locating the benchmark execution flow and the node command interface, then define the tracker’s report and discrepancy cases; done means each node can record submitted and handled transaction IDs and report lost or inconsistent transactions for benchmark validity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100