This issue came up during the e2e report generation while retrieving redemption cost:
If we're moving quickly through the deposit flow, it's possible that we will request redemption when one Infura node has minted the TBTC, but the other Infura node has not seen this yet. In this case, the TDT has not yet been transferred to the vending machine, so we call getRedemptionTbtcRequirement instead of getOwnerRedemptionTbtcRequirement. But the actual call goes to a node that has seen the minting occur, so the TDT is in the vending machine, causing the revert.
Action:
replace every call in tbtc.js with some sort of EthereumHelpers.callSafely that handles retries transparently.
This issue came up during the
e2ereport generation while retrieving redemption cost:Action:
replace every
callintbtc.jswith some sort ofEthereumHelpers.callSafelythat handles retries transparently.