IntersectMBO / IntersectMBO/ouroboros-consensus

`ChainDBLedgerInterface` could probably use a `LedgerDB` instead

Open
#1,325 0 comments 0 reactions 0 assignees View on GitHub
good first issue UTxO-HD
Dominant language
Haskell
Stars
67
Forks
43
Avg merge
5d 13h
Merged PRs (30d)
43

Description

As noted by Alex [here](https://github.com/IntersectMBO/ouroboros-consensus/pull/1267#discussion_r1837287067) the ChainDBLedgerInterface probably does not need a full ChainDB, but just a LedgerDB would be enough, and we move forward in decoupling components.

Contributor guide

Open the contributing guide

Research direction

Start by reading the ChainDBLedgerInterface and the discussion linked in the issue, then trace how it currently receives or uses ChainDB. Determine the LedgerDB boundary needed for the interface and update the affected integration points so it no longer depends on a full ChainDB. Done means the components are decoupled without changing their intended ledger behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
blockchain
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.