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
{{ message }}
This repository was archived by the owner on Jun 11, 2024. It is now read-only.
The send method of the interoperability module receives an optional timestamp parameter, which is not specified in the LIP and may lead to crashes when not set.
On sends originating from the mainchain, the timestamp parameter is used to check the liveness of a chain with the isLive) function (sidechains do not check the liveliness of other chains). So, if this optional parameter is not set when calling send on the mainchain, the code will throw an exception. This is what happens with the transferCrossChain method of the token module which does not pass a timestamp to the send function. If the mainchain uses the transferCrossChain method, the send will unconditionally fail because the isLive function throws an exception when trying to use the undefined timestamp.
Affected Version
v6.0.0-beta.2
The text was updated successfully, but these errors were encountered:
Description
The send method of the interoperability module receives an optional timestamp parameter, which is not specified in the LIP and may lead to crashes when not set.
https://github.com/LiskHQ/lisk-sdk/blob/89e7504ef5eb6183aefe576a93be3d6052e56038/framework/src/modules/interoperability/base_interoperability_method.ts#L125-L147
On sends originating from the mainchain, the timestamp parameter is used to check the liveness of a chain with the isLive) function (sidechains do not check the liveliness of other chains). So, if this optional parameter is not set when calling send on the mainchain, the code will throw an exception. This is what happens with the transferCrossChain method of the token module which does not pass a timestamp to the send function. If the mainchain uses the transferCrossChain method, the send will unconditionally fail because the isLive function throws an exception when trying to use the undefined timestamp.
Affected Version
v6.0.0-beta.2
The text was updated successfully, but these errors were encountered: