informalsystems / informalsystems/emerald
chore(state): Save validator set in shim layer state
Open
enhancement
- Dominant language
- Rust
- Stars
- 25
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Currently, Emerald always asks the smart contract for the current validator set. Ideally we should have this state in our local DB to avoid calls to fetch the valset.
These entries would be added to the database on start of the node and when the validator set changes.
Possible we'd have to still call into the execution engine on `Decided` but we will save calls in other places.
Contributor guide
Assessment
This issue has not been assessed yet.