package
0.10.3
Repository: https://github.com/tendermint/light-client.git
Documentation: pkg.go.dev

# Packages

No description provided by the author
No description provided by the author

# Functions

No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
GenSecValKeys produces an array of secp256k1 private keys to generate commits.
GenValKeys produces an array of private keys to generate commits.
IsNoPathFoundErr checks whether an error is due to no path of validators in provider from where we are to where we want to be.
No description provided by the author
IsSeedNotFoundErr checks whether an error is due to missing data.
IsTooMuchChangeErr checks whether and error is due to too much change between these validators sets.
IsValidatorsChangedErr checks whether and error is due to a differing validator set.
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
VerifyCommitAny will check to see if the set would be valid with a different validator set.

# Variables

No description provided by the author

# Structs

CacheProvider allows you to place one or more caches in front of a source Provider.
DynamicCertifier uses a StaticCertifier to evaluate the checkpoint but allows for a change, if we present enough proof TODO: do we keep a long history so we can use our memory to validate checkpoints from previously valid validator sets????.
No description provided by the author
No description provided by the author
MissingProvider doens't store anything, always a miss Designed as a mock for testing.
Seed is a checkpoint and the actual validator set, the base info you need to update to a given point, assuming knowledge of some previous validator set.
StaticCertifier assumes a static set of validators, set on initilization and checks against them.

# Interfaces

Provider is used to get more validators by other means TODO: Also FileStoreProvider, NodeProvider, ...

# Type aliases

No description provided by the author
Test Helper: ValKeys lets us simulate signing with many keys.