1/ *Centralized* apps building atop decentralized protocols may be the winning combination, each furthering the adoption of the other.

2/ As many have pointed out, “decentralize all the things” is a mistake. Decentralize the things that benefit from decentralization.
3/ Starting with centralized apps (think @coinbase @circlepay etc), if you’ve been paying attention, they are utilizing an increasing amount of decentralized protocols & open-source crypto infrastructure, to the benefit of their end users.
4/ The realization this week that @coinbase and @circlepay built their #stablecoin on top of @zeppelin_os was another tick in this trend. https://t.co/rpgyQJ8Sdo
5/ Centralized #crypto apps that build upon decentralized protocols have:

-Global capabilities from day one
-Lower costs due to the on-demand and perfect-competition nature of protocol services
-More rapid innovation as they build upon others’ open source building blocks.
6/ Long term, centralized #crypto apps that build atop decentralized infrastructure will find it the key to what allows them to scale beyond, and outcompete, incumbents that fear public networks & cling to owning their infrastructure.
7/ Having covered cloud companies for 3 years & seeing how long it took big incumbents to embrace the public cloud (and some still haven’t), I have a hard time seeing these incumbents embrace decentralized protocols before it’s too late. Their loss.
8/ All of this leaves decentralized apps (#dapps) in hot water. As many have been pointing out, pure-play dapps are not getting much use.
9/ Connection points to end users need to be hyper-responsive, and due to the laws of physics, #dapps are fighting an uphill battle against centralized apps in response times.
10/ Projects like @graphprotocol or Picolo Network (https://t.co/hd1aN5nO0s) are aiming to help #dapps with their response times, but it remains TBD if it will ever be good enough for a human to not discern the lag.
11/ I also think customer service via #dapps is going to be a hard problem to solve, as customer service is high-touch and doesn’t come for free.
12/ Centralized apps in #crypto also currently have the vast majority of *distribution* to the end user, which so long as they continue to remain technologically relevant I have a hard time seeing them cede to #dapps.
13/ For these reasons, if you’re focusing on investing in #cryptoassets (as @placeholdervc is), I recommend focusing on layer 1 protocols, and important middleware protocols atop the layer 1’s.
14/ Look at what protocols the centralized apps are building atop, and getting real utility out of.

Those will have fundamental value, regardless of how much some obsess over “economic abstraction” and “infinite velocity.”
15/ As always, I’m open to being proved wrong, but I feel reasonably confident that in the short-to-medium term it will be the centralized apps that continue to capture most all of the users — longer term, as people work to make dapps more responsive, we’ll see.

More from Tech

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.

You May Also Like

दधीचि ऋषि को मनाही थी कि वह अश्विनी कुमारों को किसी भी अवस्था में ब्रह्मविद्या का उपदेश नहीं दें। ये आदेश देवराज इन्द्र का था।वह नहीं चाहते थे कि उनके सिंहासन को प्रत्यक्ष या परोक्ष रुप से कोई भी खतरा हो।मगर जब अश्विनी कुमारों ने सहृदय प्रार्थना की तो महर्षि सहर्ष मान गए।


और उन्होनें ब्रह्मविद्या का ज्ञान अश्विनि कुमारों को दे दिया। गुप्तचरों के माध्यम से जब खबर इन्द्रदेव तक पहुंची तो वे क्रोध में खड़ग ले कर गए और महर्षि दधीचि का सर धड़ से अलग कर दिया।मगर अश्विनी कुमार भी कहां चुप बैठने वाले थे।उन्होने तुरंत एक अश्व का सिर महर्षि के धड़ पे...


...प्रत्यारोपित कर उन्हें जीवित रख लिया।उस दिन के पश्चात महर्षि दधीचि अश्वशिरा भी कहलाए जाने लगे।अब आगे सुनिये की किस प्रकार महर्षि दधीचि का सर काटने वाले इन्द्र कैसे अपनी रक्षा हेतु उनके आगे गिड़गिड़ाए ।

एक बार देवराज इन्द्र अपनी सभा में बैठे थे, तो उन्हे खुद पर अभिमान हो आया।


वे सोचने लगे कि हम तीनों लोकों के स्वामी हैं। ब्राह्मण हमें यज्ञ में आहुति देते हैं और हमारी उपासना करते हैं। फिर हम सामान्य ब्राह्मण बृहस्पति से क्यों डरते हैं ?उनके आने पर क्यों खड़े हो जाते हैं?वे तो हमारी जीविका से पलते हैं। देवर्षि बृहस्पति देवताओं के गुरु थे।

अभिमान के कारण ऋषि बृहस्पति के पधारने पर न तो इन्द्र ही खड़े हुए और न ही अन्य देवों को खड़े होने दिया।देवगुरु बृहस्पति इन्द्र का ये कठोर दुर्व्यवहार देख कर चुप चाप वहां से लौट गए।कुछ देर पश्चात जब देवराज का मद उतरा तो उन्हे अपनी गलती का एहसास हुआ।