You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sendTransaction() - To interact with contracts, it'll be important to be able to sendTransaction() as well, one where gas is paid for X thing to happen, but not send additional X token on top of the gas (i.e. not meant for money sending, like send() presumably is above)
Also, we'll need to be able to support contract deployments, it's technically a transaction just like any other, but I want to call it out distinctly.
Finally it's hard to talk about specifics like this without knowing at least one chain that we intend to support- this is something we need to decide on soon, before implementation can really begin. For example, if on Ethereum, we would need distinct transaction types for sending native Eth, and another for sending ERC20s, and so on (swap in BSC, et. al. if you like). The point is that each token standard has their own set of checks/balances that are required to safely send/receive
The text was updated successfully, but these errors were encountered: