Ethereum State rent for Eth 1.x pre-EIP document

Not really; I’m highlighting that requiring signed ACKs for token transfers brings it very close to the existing allowance model.

A comparison (might work better in table format?..):

  • in your (proposed) REQ/ACK transfer scheme:
    • the sender needs to first obtain a REQ/ACK from the receiver, and then
    • perform the transfer themselves;
    • they can’t transfer more than their balance;
    • displaying balances is supported by wallet software;
  • in the (existing) allowance scheme:
    • the sender first sets an allowance, and then
    • waits for a receiver-initiated ACK;
    • can set allowances in excess of their balance, although no more than the balance can actually be claimed by the receivers;
    • displaying allowances - from self or to self - is not supported by any wallet software I know of.

There are subtle differences between the two, and I find both schemes useful.

If anything, so far, this is not (yet) a critique, but a note of agreement and support. :fireworks:


Sorry if that’s the impression my reply gave.

My actual critique is that, as long as there are protocol- and contract-level features (such as allowances or rent) of which wallet-level software is unaware of (and leaves the user unaware of), we will remain in this ditch of trying to solve application-level (both wallet- and game-) problems with protocol-level tools only. Or on the application-level only.

Note that:

  • I’m not referring to the particular balance- or allowance-grieving attacks, which become such with the introduction of rent. Both of these
    • can be solved partially (on the contract-level) with the introduction of time-outs for transfers/allowances, as I’ve mentioned in previous reply; and
    • can probably be solved completely (on the protocol-level) by use of cross-contract storage, as you describe in the slides. (Although, must I say, the images there lack legends, so aren’t very approachable. I’ll go read the comments here and on Reddit before asking for clarifications.)
  • By “game-level problems”, I mean not zombie-cat-warrior toys, but application-level design choices that are mainly game-theoretic; the kind in the saying “if you don’t understand the game, then you’re it”.

My main critique is on the disconnect between actors at various levels in the ecosystem, not your slides. Which why I called my first comment “discussion-derailing”. :slight_smile:

[rant snipped as hindsight]

There are ways to mitigate state growth in the interim, while rent is being developed; but the mitigation would have to come from actors - wallet and game developers - that are indifferent, because they are not being penalised yet. “Oh well”.

1 Like