v17.4+ writes interior trie nodes to the takeover db
Open
- Dominant language
- C++
- Stars
- 2.5k
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
For example, see:
`
select distinct name from takeover t where t.height = 658309 and name not in (select distinct nodeName from claim);
`
It looks like one third of the nodes in the takeover table are invalid. It's a minor performance issue.
Contributor guide
Research direction
Start by reproducing the reported query against the takeover and claim tables at height 658309. Trace where trie nodes are written to the takeover database and compare the stored names with claim.nodeName. Done means interior or otherwise invalid nodes are no longer written to takeover, reducing the reported invalid rows without changing valid entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- blockchain, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100