Thomas Nguy

One solution could be to invalidate /cancel "all" the transaction in the batch. But that may affect innocent users

yes that is correct. Also the fact that all txs are batched create more complex situation to handle individual failure I think ideally, we could catch the "revert" in the...

USDC and USDT have special logic such as "Blacklist" functionality https://etherscan.io/address/0xdac17f958d2ee523a2206206994597c13d831ec7#code while some addresses (such as zero address) are predictable, the list can be updated dynamically so it is hard...

One more controversial solution is just to ignore the revert in the smart contract. The user sending the "bad transaction" will lose money but at least the other transactions will...

`Lose money means the bridged funds are lost too?` Lose money means that tokens will be burn on cronos but the receiver will not receive its token. Technically the token...

We can add an event in case the transaction is reverted that can be relayed back. For since the contract has an admin, the claim would be done through manual...

I have proposed a POC here to solve this issue relying only on the smart contract https://github.com/crypto-org-chain/gravity-bridge/pull/67

I think there is no concept of timeout for send_to_ethereum. Means that this operation is irreversible. It is possible to cancel if the transaction is not included in a batch,...

is it still a draft ? @calvinaco

hi @EricBolten how the minimum fee would be calculated? would it be a fix percentage of the transported token or relaying on some oracle?