Richsun

Original text: Thin Applications —— Placeholder

Translator: Evelyn｜W3.Hitchhiker

When I started thinking about the architecture of blockchain applications in 2014, I described it as a layered "stack" of functionality. The first iteration described a blockchain-based "overlay networks" on which specific decentralized services are provided, forming a "shared" protocol and data layer. On top of them, independent applications will consume these protocols and redistribute their services to users.

"Blockchain Application Stack" (2014)

Original text: Fat Protocols —— Placeholder

Translator: Evelyn｜W3.Hitchhiker

Note: Please see the follow-up article in 2020: "Thin Applications"

Here’s one way to think about the differences between the Internet and blockchain. The previous generation of sharing protocols (TCP/IP, HTTP, SMTP, etc.) produced immeasurable value, but much of it was captured primarily in the form of data (think Google, Facebook, etc.) and reintegrated at the application layer. In terms of how value is distributed, the Internet stack is made up of "thin" protocols and "fat" applications. As the market has evolved, we have learned that investing in applications yields high returns, while investing directly in protocol technology often yields low returns.

Author: Xiang｜W3.Hitchhiker

Revision: Evelyn｜W3.Hitchhiker



4844 and 4488 on the market have been promoted many times. Apart from this huge publicity effect, EIP-4804 is actually an EIP that deserves attention.

Simply put, EIP-4804 provides Web2 users with a simple way to directly access Web3 content. Currently, Web3 reading data usually relies on the translation of Web2 proxies to the Web3 blockchain. However, the translation is mostly completed by agents such as dApp websites/node service providers/etherscan and is not controlled by users.

Original text: Variable security data sharding —— polynya

Translator: Evelyn｜W3.Hitchhiker

Disclaimer: Everything here is purely speculative thinking, there are many oversimplifications, none of this should be taken seriously, I just hope there is some food for thought.

The beautiful idea of ​​Danksharding is this: only the builder (which is an honest minority assumption anyway) will need to run the expensive hardware. Over time, rollups scale to millions of TPS at very minimal cost to validators, users, and everyone else. The problem is, this ambitious vision will take time to prove. It could be anywhere from 2 to 5 years, depending on who I ask of course. While the crypto space has always suffered from the extreme planning fallacy, things are definitely improving, but I refuse to trust any roadmap until I can see a fully functional prototype emerging.