search

openwallet-foundation / architecture-sig

This special interest group (SIG) is focused on conversations related to the architecture of digital wallet engines and is a sub-group reporting to the OpenWallet Foundation's Technical Advisory Committee.
Creative Commons Attribution 4.0 International
42 stars 16 forks source link

Crypto Currency #2

Open OR13 opened 1 year ago

OR13 commented 1 year ago
ghost commented 1 year ago

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