(2/) The price we pay for these: 1. Lack of confidentiality for our code, 2. Huge performance penalty. We now try to fix both problems by reducing decentralization: offchain computation in TEEs like SGX (which always will have single root of trust -- CPU vendors), sharding.
-
-
Show this thread
-
(3/) The "decentralization" is a mere implementation detail. OT1H it allows us to have integrity and availability for our code, OT2H it ruins privacy and performance. The challenge is to find the right tradeoff. But "decentralization" doesn't give us anything in itself, does it?
Show this thread -
(4/) So, if I could, say, launch a traditional server onto an Earth's orbit, perhaps this would be "reasonably" as good a solution as Ethereum? Assuming the root account was disabled and the cost of shooting it down (physically) was high enough?
Show this thread
End of conversation
New conversation -
-
-
By essential feature do you mean what is advertised or what dapp developers and end-users' want/expect?
-
Users, in general, be that end-users or developers.
-
Users want to be sure their transactions are: * Pseudonymous (which is often confused for private!) * Safe (free of unintended side-effects) * Unstoppable (some validator can always be accessed and used. Most users expect this to be a 3rd party, which breaks the model.)
-
Interesting you're looking at things from the transactions pov, while I'm seeing things from the computing platform pov.
-
The users in the space are somewhat odd, they want an alternate computing substrate, but they don't entirely realize this, so it requires looking at the problem from top and bottom. The general ignorance regarding anything RF in the space is almost as troubling as the OPSEC.
End of conversation
New conversation -
-
-
You can have these features just by widely distributing a signed copy of your code. What ethereum gives you that this doesn't is consensus: broad agreement on the state produced by running your code.
-
And in that vein, guess it's the consensus mechanism over a bunch of signed transactions that is "the computer". The EVM bit is a feature that let's you reduce those statements into a convinient view.
End of conversation
New conversation -
-
-
You forgot one essential feature: to make the creators rich even if they don't provide what they promised.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
"2. strong availability for your code." By this, i'm assuming you mean robustness? The part of this that I care about more is resistance to censorship. There is a lot of good that can be contributed to by the use of these types of technologies.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
3. Create cookie cutter tokens to sell to suckers and not run any code due to slowness and bloating.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Those words don't exist if you read the white papers
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.