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
however, when we call it from TokenVault.sendEther, we do this:
message.gasLimit = gasLimit;
message.processingFee = processingFee;
message.depositValue = msg.value;
message.refundAddress = refundAddress;
message.memo = memo;
// Ether are held by the Bridge on L1 and by the EtherVault on L2, not
// the TokenVault
bytes32 signal = IBridge(resolve("bridge")).sendMessage{
value: msg.value
}(message);
ie: it is imposible for msg.value to be equal to the message.deposit + call + processing amount, because depositValue on message is ALWAYS set to msg.value.
The text was updated successfully, but these errors were encountered:
cyberhorsey
changed the title
[protocol] bug - TokenVault unable to send message with processingFee > 0
[bridge] bug - TokenVault unable to send message with processingFee > 0
Nov 15, 2022
in Bridge.sol when we check the .sendMessage call from TokenVault, we have this check:
however, when we call it from TokenVault.sendEther, we do this:
ie: it is imposible for msg.value to be equal to the message.deposit + call + processing amount, because depositValue on message is ALWAYS set to msg.value.
The text was updated successfully, but these errors were encountered: