The problem with stateless ethereum is that it weakens and threatens the separation between dapp development, hosting, and use
Will users host and provide up to date state? Will application developers? It isn’t clear — but what is clear is that for some state in some cases that it won’t be hosted by block producers
Mar 30, 2019 • 4 tweets • 1 min read
It's not failing, it was never set up to deal with changes that are driven by non-technical considerations, and people have regrettably been trying to use a system for tech changes to make non-technically motivated decisions
We should replace the whole question of "when does a token go from being a security to being a commodity?" with "is this token being bought/sold as a security or as a commodity?" for every individual sale/purchase basis
And then we can look at the volume of sales of tokens that are sold as securities vs as commodities, if we think that it's meaningful to ask whether the token itself (as opposed to how it is used) is a commodity or a security
Dec 17, 2017 • 10 tweets • 3 min read
I think this is a fundamental tradeoff in fault tolerant consensus protocols. (Thread!)
Consensus protocols that only create finalized blocks have low latency and parametrizations in the purple area below (though their overheads for any different node counts may vary).
