Reducing the unbonding period on an IBC enabled chain cannot be done this way.
The trusting period of the IBC client on counterpaty chains are set to 2/3 of 30 days => 20 days
The “trusting period” refers to the length of time during which an IBC client considers the proofs provided by the counterparty chain to be valid, without needing to actively verify them.
On the other hand, the “unbonding period” is the period during which tokens are blocked after being delegated to a validator before they can be withdrawn.
The rule stipulating that an IBC client must not have a trusting period greater than the unbonding period of the counterparty chain is based on security considerations.
-
Double-spending risk: If an IBC customer’s trust period is longer than the unbonding period on the counterpart chain, this could create a double-spending risk.
For example, if a user delegates his tokens to a validator on chain A, then withdraws them after the unbonding period on chain B, and if chain A doesn’t have a trust period long enough to detect this, there could be a state validity conflict between the two chains. -
State synchronization: The trusting period is linked to the synchronization of states between chains.
If the trust period is longer than the unbonding period, this means that the IBC client may accept obsolete evidence for a longer period, which could lead to a state divergence between the chains. -
Security and integrity: To guarantee the security and integrity of transactions between chains, it is essential that the IBC client can quickly detect malicious manipulation of the counterparty chain.
limiting the period of trust to the unbonding period ensures that the evidence provided remains relevant and valid. In practice, we choose durations of 2/3.
In short, the rule of not having a trusting period greater than the unbonding period is designed to guarantee the security and integrity of transactions between chains in a Cosmos-SDK and IBC environment.
David
Crosnest Validator