Summary
The light client that gets created by quartz uses a single trusted height through all its life.
The trusted height should be periodically updated, the same way it needs to be updated with IBC protocol.
Context:
There is meaning attached to the trusted_height. Usually the trusted height needs to fall into inside the unbonding period of the chain (usually it's configured to be 2/3 of the unbonding period). Any requests that are referencing states outside the trusting period (before the trusted height) need to be rejected because the client may be malicious or too far out of date.
Summary
The light client that gets created by quartz uses a single trusted height through all its life.
The trusted height should be periodically updated, the same way it needs to be updated with IBC protocol.
Context:
There is meaning attached to the
trusted_height. Usually the trusted height needs to fall into inside the unbonding period of the chain (usually it's configured to be 2/3 of the unbonding period). Any requests that are referencing states outside the trusting period (before the trusted height) need to be rejected because the client may be malicious or too far out of date.