Height <-> ValsetUpdateID mapping is inefficient #718
Labels
S: ImprovingThings
Improving things: Customer requests, performance improvements, reliability and usability
source: audit
To indicate an issue found during an audit.
type: feature-request
New feature or request improvement
type: tech-debt
Slows down development in the long run
At the moment, we save a mapping to valset updateID at every height. This is a new key added every block even if the valset hasn't changed.
We can instead only store the mapping on the height at which the valset is updated.
We can still recover the relevant valsetUpdateID for a given infraction height by using iterators.
Not necessary for first release perhaps, but this is a clear optimization that may prove necessary later on
The text was updated successfully, but these errors were encountered: