We have found a critical bug in the Bittensor EVM deployment whereby whatever you set as gas limit is consumed as gas spend. Every EVM dapp, developer, and wallet works under the assumption that unused gas is refunded. All developer tooling also assumes this (such as hardhat, which you have in docs). The most popular wallets do their own gas estimate and then increase it by 50% by default, for example. Unfortunately in this deployment the gas limit acts as the amount that is consumed no matter how much the transaction would have consumed. Given the lack of clear documentation on the EVM implementation and barely functional block explorer, its not quite clear where exactly this gas gets sent to. Its insane that something so simple has made it into a production environment. This is an active bug that everyone using the EVM for any purpose will suffer from. Disclosed this to @opentensor but they are "too busy working on rao" to care - might be able to look at it in a few days and see if there is an issue. Great response guys. 🤡 Insane that such a high priority major rollout is done in such a rushed manner with little to no basic testing first - and they had the cheek to ask why we were "testing on mainnet" - why are you testing on mainnet @const_reborn??? Furthermore, there seems to be another serious gas estimation issue that is compounding this. For example, there are 5-6 Wrapped TAO contracts that have been deployed, in all of these the standard eth_gasEstimate estimates gas consumption of 10x all the way up to the full block limit, when it should be one of the cheapest transactions. This issue is present in the wTAO contracts utilised by the two DEXes that have publicly announced and deployed on mainnet with frontends - tagging @HotKeySwap as you may want to look at this and probably want to close down your frontend on Bittensor to save user funds until this is patched. Same for any other dapps that are currently live (@CryptoEternalAI / @punk3700 / @taobnk / @TensorplexLabs not sure where you are all at with deployments?). I'd suggest that everyone refrain from using the EVM implementation and any dapps built on top of it until this is fixed. Would appreciate if people could tag other live dapps and share to save users from burning through funds in the meantime. Still want to argue that this isn't rushed and how wonderful the barely functional block explorer is @mogmachine or you're willing to admit this is a total shitshow now? Ashamed to be a $TAO bagholder here - the @opentensor dev team are still operating like this is a $10m MC shitcoin, not the leading DeAI project in the space.