4 ms·

Yes, interestingly with Ethereum it's not the individual block size that's holding it back (they're around 80kb), it's the protected size of all blocks for peop

Yes, interestingly with Ethereum it's not the individual block size that's holding it back (they're around 80kb), it's the protected size of all blocks for people running validator nodes. You don't want to require node operators to have 100TB in SSD storage because your blocks all pile up too quickly (this is one of the main concerns about Avalanche scaling).

thinkmassive 5y ago
Part of it IS the individual block size though. Individual blocks might seem small, but there's a lot more of them. Ethereum dApps store a LOT of state directly on the base chain. The other scalability disaster is making every node validate every instruction of a Turing-complete scripting language, which results in insane "gas fees" (or loss of fees when you didn't supply quite enough for the script to fully execute).
- jazzyjackson 5y ago
  > (or loss of fees when you didn't supply quite enough for the script to fully execute). Are they planning to address this in any of the updates on their timeline? This turned me off from ETH completely, just feels like a house-always-wins situation skimming money from users.
  - thinkmassive 5y ago
    No idea, Ethereum was an intriguing experiment for the first few years, but it’s seemed like a dead end for a while now
  - 3np 5y ago
    Since it's deterministic, you can get a good estimate (in fact exact as long as you are not front-run) by simulating the execution locally before submitting it. All major wallets do this.
  - tornato7 5y ago
    In addition to what 3np said, you can use Flashbots as your RPC node, and your transaction won't be submitted if it's going to fail. Minor note, the reason for charging for failed transactions is to prevent abuse of network resources, don't want someone submitting millions of bogus transactions to DOS the network.
    - jazzyjackson 5y ago
      That's a good reason, still need people to pay for scarce resources, just a shame that there's no mechanism to pick up where you left off. Thanks for the tip about flashbots, never heard of it

thinkmassive 5y ago

Part of it IS the individual block size though. Individual blocks might seem small, but there's a lot more of them. Ethereum dApps store a LOT of state directly on the base chain. The other scalability disaster is making every node validate every instruction of a Turing-complete scripting language, which results in insane "gas fees" (or loss of fees when you didn't supply quite enough for the script to fully execute).

jazzyjackson 5y ago
> (or loss of fees when you didn't supply quite enough for the script to fully execute). Are they planning to address this in any of the updates on their timeline? This turned me off from ETH completely, just feels like a house-always-wins situation skimming money from users.
- thinkmassive 5y ago
  No idea, Ethereum was an intriguing experiment for the first few years, but it’s seemed like a dead end for a while now
- 3np 5y ago
  Since it's deterministic, you can get a good estimate (in fact exact as long as you are not front-run) by simulating the execution locally before submitting it. All major wallets do this.
- tornato7 5y ago
  In addition to what 3np said, you can use Flashbots as your RPC node, and your transaction won't be submitted if it's going to fail. Minor note, the reason for charging for failed transactions is to prevent abuse of network resources, don't want someone submitting millions of bogus transactions to DOS the network.
  - jazzyjackson 5y ago
    That's a good reason, still need people to pay for scarce resources, just a shame that there's no mechanism to pick up where you left off. Thanks for the tip about flashbots, never heard of it