Brainstorming the token standard in eth2

[veox]

Somewhat OT:

@vbuterin

Particular issues with the standard in ETH1 include:

• Severe UX losses from needing to send multiple transactions when using a dapp that requires payment in tokens (eg. selling tokens in Uniswap): first one must send a transaction to approve the target contract’s right to withdraw tokens from the sender’s account, then one must call the target contract, at which point the target contract can then “pull” tokens from the sender’s account

“Fixing” this could be achieved differently, by changing no-destination transactions (with to=='') to have ADDRESS of the EOA (and likely fall-out changes to CREATE and CREATE2). We could then use such transactions for things other than contract deployment and graffiti.

Currently (quoting “transient” programs out of context, where I’ve touched on this briefly):

@veox

The fact that leaving the to field empty results in increased gas use - by way of a nonce d account address assignment, instead of just using the EOA’s address and deferring the nonce -ing until an actual CREATE is requested, - suggests that “contract deployment” at this point is expected.

Haven’t pondered much on whether there are concealed invariants here that might get broken. SSTORE during this lowest-level call frame might become problematic, for example.