Exposing MetaMask's Gas Estimate from the transaction insights API

[mindofmar]

Hey team. We would appreciate some guidance here on how to do gas estimations for transaction insights snaps. We tried out beaconcha.in as suggested by the Snaps Docs as well as our own gas estimation strategy but saw inconsistent gas estimations between our attempts and what MetaMask displays in the extension. Our guess is that this happens because MetaMask assumes a higher block base fee than what is currently being returned by nodes to account for spikes in gas fees.

It raises a question about the developer experience and end-user experience for gas estimations. For developers, teams might not have expertise at calculating probabilistic gas estimates based on how long it takes for a transaction to be included in the next block. For end-users, it may be confusing to see two differing gas estimates.

Would it be possible for MetaMask's gas estimation to be exposed as a param for the onTransaction function? Or, is it ok to hit MetaMask's gas API within the Snap or the Snap's backend itself.