To Web3 #1 Kick off & Content Delivery

Want to see Web3 in a logical way? Here are some frameworks and cool opinions that might help.

Thanks to those free time during Christmas and New year, I can rearrange my past thoughts about Web3. Now, I decide to start this blog- you can find analysis of frameworks, discussion about projects and strange thoughts as well.
Thanks to those free time during Christmas and New year, I can rearrange my past thoughts about Web3. Now, I decide to start this blog- you can find analysis of frameworks, discussion about projects and strange thoughts as well.


  • A framework to arrange thoughts and find missing pieces of Web3.
  • Pretty features for Web3 Project to consider: trust-less infrastructure, composable back-ends, ownership and self-sovereign identity, configurable mode and strategy.
  • Simple recommendation is needed for current content platforms; Recommendation algorithm is good but a waste for current market; Multi-Account solution is a great addition to deal with potential conflicts between recommendation and privacy issues.
  • Separating ownership and right of use is one of the most important preconditions for the creator economy.
  • AMA Collection looks forward to having more friends share thoughts!

P.S. All lists below are in no particular order.

Feature of Web3 Project

Lots of friends have already tried to give their definitions of Web3. To make my framework more logical and usable, I try to summarize some features that a Web3 project could have:

  • Trust-less, distributed and robust infrastructure
  • Composable and open back-ends
  • Configurable mode and strategy
  • Self-sovereign Identity and ownership of data
  • Native digital currency system
  • User as owner mechanism

One important point to add: although I work for a crypto VC (A&T Capital), I don’t think it is necessary for everything in Web3 to be ‘on-chain’. It is not only because of the current technical limitations, but also because of the fact that many scenarios do not need to be ‘on-chain’ >>>Web3 will be a perfect integration of ‘on-chain’ and ‘off-chain’.

General Framework

Logic of vertical classification: for any industry, the three-layer classification, namely, infra/middleware/ application, always proves effective. About MEME, it is a non-figurative representation of real-world culture in the crypto world. It should have some guiding significance for implementing traditional three layers in crypto, and it even has the potential to be a new and meaningful layer. Logic of horizontal classification: content delivery/ social/ game/ e-commerce are the most popular sub-tracks. As these four sub-tracks satisfy our basic demands which won’t change in Web3, they will still exist but might be in a different form. I add DAO here because although it hasn’t been developed very well in Web2, it will be one of the most important components of Web3. P. S. DAO, as the final fantasy of crypto culture, will definitely not be accomplished overnight. However, every step of DAO’s development will reflect the progress made in Web3 and exert considerable influence on the growth of the four sub-tracks.

Content Delivery Track

The reason why we start with the content delivery track is that it follows the rule of Web2’s development. Personal homepage/yellow pages appeared earlier than Facebook/Twitter, as primary content delivery has the simplest business logic and minimum requirements for undergirding technology. The current market has already proven the speculation above: compared with social dapps, content delivery dapps have already made some achievements!

P.S. Dapps in gray cells originated from web2, but I don’t think they need to be ‘transformed into web3’ urgently.
P.S. Dapps in gray cells originated from web2, but I don’t think they need to be ‘transformed into web3’ urgently.

Of course, there are plenty of things that can be discussed from the table above. I decide to start with two problems based on my own experiences:

  • For a content consumer, it’s too hard to find contents he wants—a simple recommendation and multi-account system could be a workable solution in the near future.

    As a content reader, I only think about three steps most of the time:

    1. How to find the content;
    2. Where I can read the content;
    3. How to make a payment.

    Currently, mirror + Ethereum + Arweave combination is not bad to solve step 2. Blockchain native payment +NFT + ENS + Revenue Distribution Tools combination can fit requirement step 3 well. But the solution to step 1 still needs to be figured out.

    Compared with search engine & recommendation algorithm in Web2 apps, it’s too hard for me to find the ideal contents in mirror—I can only mark the author’s site in mirror when I read his great contents in Twitter (Mirror doesn’t even offer me the ‘following’ function);Or type key words on AskMirror—a search engine for Mirror (as the searching results are always a little bit strange, its sorting logic need to be optimized).

    Then why not add a ‘following’ function (I can accept that Mirror wants to keep ‘pure’, but then AskMirror or a wallet can do it)? With the ‘following’ function, a social graph can be generated, followed by the recommendation. If the info pool is too small to support the algorithm, a simple recommendation based on relativity could work very well.

    If you hate being controlled by web2 giants and big data, then I have two suggestions: i. create a special account to read Mirror and do trading & other things with other accounts; ii. let users decide whether to share the history of personal transactions or not, which can be realized by a button—recommendation on/off.

    To meet requirement i, a multi-account management tool will be needed.

    To meet requirement ii, an authority management system with privacy features will be needed, but it is hard to achieve on architectures like Ethereum & Arweave which require full disclosure of information. Then, a new blockchain paradigm or on-chain & off-chain mixed storage solution might be helpful.

  • For a content creator, creator economy can’t be fully implemented without separating ownership and right of use

    As a content creator, what I care most are: support for different forms of contents, content delivery, fans accumulation and traffic monetization.

    Within the current market, traffic monetization is the biggest difference between Web3 and Web2. But the limitations of traffic monetization in Web3 are also very obvious: Pre-crowdfunding + Post-copyright income distribution is the model that we have discussed for a long time, but a good example has yet to be found. There are two reasons:

    1. Current blockchain system defines ownership very well, but the definition of right of use is lacked;
    2. Traditional off-chain solution has backup from legal system, but we currently don’t have an on-chain legal system.

    To solve problem 1, besides the on-chain & off-chain mode that I mentioned in the last case, we might also need to have authority management in account layer instead of blockchain layer. Besides, an oracle with great coverage will also be important.

    Obviously, an on-chain legal system is good, but the fact is that we need to wait for a long time to have an on-chain legal system. Before that day, Pre-staking + DAO can solve problem 2 partially (it is undeniable that the mechanism will fail if the benefit of being evil is higher than the staking value).

AMA Collections (can also be your thoughts):

P.S. Either correction or confirmation in the future will be good for our self-growth

  • Should traffic aggregation belong to the application layer or middleware layer? (Opinion from Pan_Twitter @nake13)

    It can be both, but in two different expressions. I prefer seeing it in the application layer in the early stage.

    Reasons: in the early stage, every individual application won't have a rich user base, so an aggregator/distributor platform established by a team with a user accumulation base would work very well. And in the long run, some standards that have been widely accepted might come out as middleware.

  • What will be the relationship between wallet and user entry point in Web3?(Opinion from Twitter @frank-lay2)

    Wallet can be divided into three layers: Signer (the logic of private key management) / Provider (the middle ware between Signer and dApp, e.g. the RPC calling rule from Metamask to dAPP) / Transfer logic.

    The user entry point in Web3 should be better regarding Signer, e.g. richer functions (e.g. different versions of verification, configurable encryption/decryption), better UX.

  • How to balance the pursuit of decentralization culture and necessary compromise to meet UX requirements? (Inspired by Moxie’s ‘My first impression of Web3’)

    To clarify the question: Mirror doesn’t offer follow & recommendation functions as it doesn’t want to control users via big data like Web2 does, but its UX is definitely not good. As a platform or an aggregator, Opensea inevitably goes public in an IPO, a departure from Web3's original vision, but the great UX of Opensea does help crypto world attract lots of non-crypto users.

    Things might like ‘take a slightly more indirect path to get to the final goal’: Good UX attracts more users into the crypto world, and while users enter the crypto world, they can be educated on decentralization culture. Finally, there can be a Mega with decentralization-minded employees and users. So, pls keep supporting those good projects even if they might not be that decentralization-minded at a time.

  • Does the message function need to be on-chain?

    We don’t need a completely on-chain message function, even the gas fee is not a problem. People don’t want every single message in What’s app to be on-chain, right?

    It will be enough for a message to verify ownership and non-manipulated features when needed. While to achieve this, on-chain is not the only way.

    BTW, I’m looking forward to the function that Discord/TG can be related to on-chain wallet hash.

  • Small and delicate V.S. large and complete, what a Web3 project should be like?

    Small projects with lower cost of trial-and-error can survive the fast-changing early stage of a new industry.

    Even in the mid and late stages, ‘small and delicate’ is still the best choice based on the principles of 'minimal trust requirements' and ‘composable back-ends'. If you do want to do more, you can create and combine together new entities for new ideas. Token mechanisms will help you to manage them, way better than equity.


Subscribe to toddz
Receive the latest updates directly to your inbox.
This entry has been permanently stored onchain and signed by its creator.