You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ChannelReader::host_timestamp() gets the host's timestamp to do calculations (eg. verify packet delay elapsed and check packet hasn't expired). The problem with this approach is that the host's timestamp is non-deterministic and may vary from one full node to another. ibc-go seems to solve this by using the block time of the latest block on-chain.
Version
master
Acceptance Criteria
Handlers use the latest on-chain blocks timestamp.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate milestone (priority) applied
Appropriate contributors tagged
Contributor assigned/self-assigned
PS: Many thanks to @ancazamfir for helping find this bug.
The text was updated successfully, but these errors were encountered:
Crate
ibc
Summary of Bug
ChannelReader::host_timestamp()
gets the host's timestamp to do calculations (eg. verify packet delay elapsed and check packet hasn't expired). The problem with this approach is that the host's timestamp is non-deterministic and may vary from one full node to another. ibc-go seems to solve this by using the block time of the latest block on-chain.Version
master
Acceptance Criteria
For Admin Use
PS: Many thanks to @ancazamfir for helping find this bug.
The text was updated successfully, but these errors were encountered: