Get desktop application:
View/edit binary Protocol Buffers messages
ClientConsensusStates defines all the stored consensus states for a given client.
client identifier
consensus states and their heights associated with the client
ClientUpdateProposal is a governance proposal. If it passes, the substitute client's consensus states starting from the 'initial height' are copied over to the subjects client state. The proposal handler may fail if the subject and the substitute do not match in client and chain parameters (with exception to latest height, frozen height, and chain-id). The updated client must also be valid (cannot be expired).
the title of the update proposal
the description of the proposal
the client identifier for the client to be updated if the proposal passes
the substitute client identifier for the client standing in for the subject client
the intital height to copy consensus states from the substitute to the subject
ConsensusStateWithHeight defines a consensus state with an additional height field.
Used in:
consensus state height
consensus state
Height is a monotonically increasing data type that can be compared against another Height for the purposes of updating and freezing clients Normally the RevisionHeight is incremented at each height while keeping RevisionNumber the same. However some consensus algorithms may choose to reset the height in certain conditions e.g. hard forks, state-machine breaking changes In these cases, the RevisionNumber is incremented so that height continues to be monitonically increasing even as the RevisionHeight gets reset
Used in: , , , , , ,
the revision that the client is currently on
the height within the given revision
IdentifiedClientState defines a client state with an additional client identifier field.
client identifier
client state
Params defines the set of IBC light client parameters.
allowed_clients defines the list of allowed client state types.
UpgradeProposal is a gov Content type for initiating an IBC breaking upgrade.
An UpgradedClientState must be provided to perform an IBC breaking upgrade. This will make the chain commit to the correct upgraded (self) client state before the upgrade occurs, so that connecting chains can verify that the new upgraded client is valid by verifying a proof on the previous version of the chain. This will allow IBC connections to persist smoothly across planned chain upgrades