Package client defines a provider that uses a rpcclient to get information, which is used to get new headers and validators directly from a node.

Package files defines a Provider that stores all data in the filesystem We assume the same validator hash may be reused by many different headers/Commits, and thus store it separately.

GenSecpValKeys produces an array of secp256k1 private keys to generate commits.

GenValKeys produces an array of private keys to generate commits.

NewCacheProvider returns a new provider which wraps multiple other providers.

NewDynamic returns a new dynamic certifier.

NewFullCommit returns a new FullCommit.

NewInquiringCertifier returns a new Inquiring object.

NewMemStoreProvider returns a new in-memory provider.

NewStaticCertifier returns a new certifier with a static validator set.

DynamicCertifier uses a StaticCertifier for Certify, but adds an Update method to allow for a change of validators.

FullCommit is a commit and the actual validator set, the base info you need to update to a given point, assuming knowledge of some previous validator set.

InquiringCertifier wraps a dynamic certifier and implements an auto-update strategy.

StaticCertifier assumes a static set of validators, set on initilization and checks against them.

Certifier checks the votes to make sure the block really is signed properly.

Provider is used to get more validators by other means.

Commit is basically the rpc /commit response, but extended This is the basepoint for proving anything on the blockchain.

ValKeys is a helper for testing.