I signed a proposal to be executed by Defender with an EOA, the transaction was taking some time to execute so I decided to bump its gas fee via Metamask, hence submitted a replacement transaction on my own. The replacement transaction went through and now the proposal in Defender is stuck indefinitely in the Executing state. I understand I should probably not have messed up with Defender's transaction execution, wondering whether the proposal can be moved into Executed state somehow and what are the team's thoughts on how to handle these cases going forward.
Hi @kargakis, thanks for reaching out. Yes indeed, Defender does not still support speed ups. We will work on this eventually (hopefully soon, but I need to check with the rest of the team to be sure). In the meantime, if you paste here the proposal URL and the URL of the successful TX in Etherscan I can take care of moving it to executed as you suggest.
Hi @MartinVerzilli thanks for the prompt response!
Proposal: https://defender.openzeppelin.com/#/admin/contracts/mumbai-0xf2438A14f668b1bbA53408346288f3d7C71c10a1/proposals/2d0b8a9d-5ae3-492f-8fe5-bb42dc8e8b64
Successful replacement tx: https://mumbai.polygonscan.com/tx/0xaf48b2962d97c7eea8d7b5980d215ef74be9d52e7958432581345eedf6c46257
Done, would you check if everything looks good on your side and let me know?
Looks good now, thanks!
1 Like