Skip to content
This repository has been archived by the owner on Jun 3, 2020. It is now read-only.

Validate chains are registered on startup #376

Merged
merged 1 commit into from
Dec 13, 2019

Conversation

tarcieri
Copy link
Contributor

Previously chains were checked lazily at the time their pubkeys were fetched or signing was requested.

This adds an eager check at the time clients start.

It would probably be better if this check mapped to some sort of known-good handle (e.g. Index into a generational arena), but this is enough to catch the error eagerly instead of lazily.

I encountered this personally during the cosmoshub-3 upgrade.

Previously chains were checked lazily at the time their pubkeys were
fetched or signing was requested.

This adds an eager check at the time clients start.

It would probably be better if this check mapped to some sort of
known-good handle (e.g. `Index` into a generational arena), but this
is enough to catch the error eagerly instead of lazily.

I encountered this personally during the `cosmoshub-3` upgrade.
@tarcieri tarcieri merged commit b54f4a6 into master Dec 13, 2019
@tarcieri tarcieri deleted the validate-chains-are-registered-on-startup branch December 13, 2019 01:16
@tarcieri tarcieri mentioned this pull request Dec 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants