Prediction: Users and developers will care even more about decentralized systems, but not for the reasons you think. Here’s the gist:
Blockchains are inherently open systems. Anyone can deploy an app, become a user, or build on other people’s work.
In contrast, traditional web apps are all about collecting data. Facebook, Google, and Amazon are examples of data companies that created massive proprietary databases and fed off users’ data to profit.
You cannot do this on decentralized stacks. Data is available to anyone. You can build a better analytics engine, APIs, or a front-end. But anyone can enter the market, read all the data from the ledgers, and offer a better product.
The result: a highly competitive environment and fast innovation cycles.
As a developer, you’ll have an option: build on a trad stack or a decentralized stack. In the trad stack, you can play the “data” game but won’t be able to a) leverage existing communities, b) build on other apps, c) build on other apps’ data as easily.
In contrast, building on a decentralized stack will allow you to compose with existing userbases, communities, apps, and tooling. Only through decentralization can you ensure growth without borders.
Combining competitive env, rapid innovation, composability, and growth factors will result in better products, and that’s what users want.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Sergey Gorbunov

Sergey Gorbunov Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @sergey_nog

12 Oct
Almost "everything" you need to know about fully homomorphic encryption and how it can solve (at least some) of our data privacy problems.
The problem was first introduced by Rivest, Adleman, and Dertouzos all the way back in 1978. luca-giuzzi.unibs.it/corsi/Support/…
On a high level, an encryption scheme is homomorphic if one can perform field operations over the encrypted messages, E(a) and E(b), that result in simple base operations over the underlying encrypted values.
Read 23 tweets
6 Oct
Have you ever wondered why Threshold ECDSA is painful, Threshold Schnorr is straightforward, and Threshold BLS is trivial? Here's an informal explanation:
Everything comes down to the complexity of the signing equation for each scheme.

All secrets in all schemes are typically distributed across users using Shamir's secret sharing techniques. en.wikipedia.org/wiki/Shamir%27…
Threshold ECDSA sign equation involves multiplication of two secrets (k^{-1} and x, where x is the secret).
s = k^{-1} * (Hash(v) + r * x)

This is not straightforward!
Read 10 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(