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
If a transaction is made to a payable function, and we need the value to be incorporated in the model to reflect logic in the function body, we can use the convention of if a transaction has a value (Wei used as standard), instead of looking for the function name in the DCR ids, you look for functionName+Value => So, a transaction with some wei to a payable function extendLockTime will result in the monitor look for extendLockTimeValue function (setting the data attribute to msg.value of the transaction).
The text was updated successfully, but these errors were encountered:
If a transaction is made to a payable function, and we need the value to be incorporated in the model to reflect logic in the function body, we can use the convention of if a transaction has a value (Wei used as standard), instead of looking for the function name in the DCR ids, you look for functionName+Value => So, a transaction with some wei to a payable function extendLockTime will result in the monitor look for extendLockTimeValue function (setting the data attribute to msg.value of the transaction).
The text was updated successfully, but these errors were encountered: