At MetaMask, we care about transactions getting on-chain. Historically, this hasn’t always been the case. The first version of MetaMask just signed transactions; you had to provide your own RPC provider. Once the transaction was submitted, it was up to the RPC to get it on-chain. We see RPC providers offering things like reinforced transactions from Alchamy and transaction assurance from Infura. And in MetaMask, transactions are resent to the RPC provider if the transaction isn’t getting included. The problem is that most users don’t care about how any of this stuff works. What they do care about is why their transaction isn’t getting on-chain. So we try and abstract some of that complexity away for them with things like gas parameter recommendations and basic simulations. But at the end of the day, if a transaction doesn’t land, it’s perceived as a problem with MetaMask.
[Read More]