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 has been archived by the owner on Jun 11, 2024. It is now read-only.
if the beforeCrossChainMessageForwarding function of the token module should only work with LSK, then add a check to ensure that messageFeeTokenID is always LSK. Create a function that, given a CCM, returns the messageFeeTokenID. This will reduce the ambiguity of using receivingChainID or sendingChainID, and ensure that all functions use the same.
Add getMessageFeeTokenIDFromCCM method to Interoperability module
Description
if the
beforeCrossChainMessageForwarding
function of the token module should only work with LSK, then add a check to ensure thatmessageFeeTokenID
is alwaysLSK
. Create a function that, given a CCM, returns themessageFeeTokenID
. This will reduce the ambiguity of usingreceivingChainID
orsendingChainID
, and ensure that all functions use the same.Acceptance Criteria
Additional Information
Relevant LIP PRs,
beforeCrossChainMessageForwarding
in LIP 0051 to checkmessageFeeTokenID
lips#426getMessageFeeTokenIDFromCCM
method to Interoperability module lips#437The text was updated successfully, but these errors were encountered: