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
It's not exactly fully true, because we send that field in TransferMessage. End some other users, that can use custom Engine - can use it in their our mind.
In current pipeline for transferring the Eth from Ethereum to Near, we initiate the transfer on Ethereum side by calling the
depositToNear
in EthCustodian contract (https://github.com/aurora-is-near/eth-connector/blob/master/eth-custodian/contracts/EthCustodian.sol#L86). After that theDeposited
event is created. And thisDeposited
event contains thefee
field.According to:
We would like to transfer the
amount - fee
to thenew_owner
and thefee
to therelayer
. But in current realization we transfer theamount
to thenew_owner
and nothing torelayer
: https://github.com/aurora-is-near/aurora-eth-connector/blob/master/eth-connector/src/lib.rs#L563PR with this changes: #16
I propose to add comments in all contracts that it is deprecated field and extra check that
fee == 0
into EthCustodian contract.The text was updated successfully, but these errors were encountered: