Consider storing the sum tree as a dynamic array
Open
- Dominant language
- Solidity
- Stars
- 20
- Forks
- 17
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 4
Description
Right now, it's stored as a mapping. Unfortunately, that means:
1. We waste a hash syscall every time we do a lookup (not huge).
2. Every step will access a random slot which will lead to an IPLD load.
If we switch to a dynamic array, I _think_ the last 5 steps (once we're within 5 bits of the target) should all fall within 1-2 IPLD nodes so we should save 4-5 IPLD loads every time we search.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.