Ncookie

Setting the default wallet to `None` on `brave://settings/wallet` seems to avoid the errors on my end. 

Also seeing this error message on Brave, more specifically both `chainId` errors. On my end this is the case on all sites (including GitHub right now). Updated the extension and...

In retrospect, this is most likely a Brave issue, not a MetaMask issue - setting the default wallet to `None` on `brave://settings/wallet` seems to avoid the error. 

This should really be merged :3

+1 This is likely a CORS setup issue on the worker in question, so hopefully this is resolved soon ;-; Not much we can do on this end.

> it's best to set the token approve amount to match the transaction amount by default Absolutely. But the transaction request is made by the dapp you're interacting with, not...

> Do you enjoy using our interface in the Send flow? Are you missing any features here? I really like it! For something like a simple transfer event there's really...

> * You will also start to see more rich data when we roll out transaction simulation in the coming weeks. Just want to give props to the team for...

> Since there's no pagination, it’s un-intuitive to show data that is not currently seen by the user I agree, but I think adding some form of pagination would be...