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
#2176 did not help. Apparently, we have somewhere a bug with internalize flag, because transaction that get internalized (0x577767a68da9ad92d29986679ae30cd27c7394d20d91bb42c22bf61a42f49110) still return revertable() == true.
There might be several problems here:
How did we end up internalizing the settlement with interaction having internalize==false.
Do we properly propagate internalize flag from solvers? AFAIS they are sending false for these simple interactions, why would they? It's in their interest to allow it for lower costs.
The transaction you shared here is actually not an internalisation but one CoW Swap order + a single interaction which is a private market maker trade.
Technically, those pose no MEV risk neither and thus don't require private submission, but right now we have no way to identify if an interaction is "risky"
Please let me know if there are other examples of this, or if the issue can be closed.
Problem
#2176 did not help. Apparently, we have somewhere a bug with internalize flag, because transaction that get internalized (0x577767a68da9ad92d29986679ae30cd27c7394d20d91bb42c22bf61a42f49110) still return
revertable() == true
.There might be several problems here:
internalize==false
.Impact
Spending more gas than necessary.
To reproduce
Analyze the driver logs for the example transaction
0x577767a68da9ad92d29986679ae30cd27c7394d20d91bb42c22bf61a42f49110
Expected behaviour
We should have not disabled the Mempool in this case.
The text was updated successfully, but these errors were encountered: