IntersectMBO / IntersectMBO/cardano-ledger
Do pulsing on ticks that don't have blocks
- Dominant language
- Haskell
- Stars
- 295
- Forks
- 179
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 29
Description
This will require support from consensus.
TICK rule will need a new argument that says is there a block being processed on that tick or not
On the TICKs that don't have any blocks is the time when we need to do all pulsing and omit pulsing on the TICKs that do process blocks
This will improve propagation times, because block validation will not be affected by pulsers and will spread out pulsing computation much better.
Contributor guide
Research direction
Start by reviewing the TICK rule and the consensus support mentioned in the issue. Trace how ticks with and without blocks are represented, then establish the required behavior for pulsing on those ticks. Done means the consensus and ledger changes are agreed and covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100