<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Louis Moynihan on Medium]]></title>
        <description><![CDATA[Stories by Louis Moynihan on Medium]]></description>
        <link>https://medium.com/@louis.moyn?source=rss-17fef825e523------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7CF_ark9hg8eyVSjAnX-7w.png</url>
            <title>Stories by Louis Moynihan on Medium</title>
            <link>https://medium.com/@louis.moyn?source=rss-17fef825e523------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:23:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@louis.moyn/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ERC-4337 & Web3 Messaging]]></title>
            <link>https://medium.com/@louis.moyn/erc-4337-web3-messaging-7d644deddcd5?source=rss-17fef825e523------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d644deddcd5</guid>
            <category><![CDATA[erc-4337]]></category>
            <category><![CDATA[web3-wallet]]></category>
            <category><![CDATA[web3-messaging]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <dc:creator><![CDATA[Louis Moynihan]]></dc:creator>
            <pubDate>Tue, 21 Mar 2023 02:58:21 GMT</pubDate>
            <atom:updated>2023-04-17T23:58:10.926Z</atom:updated>
            <content:encoded><![CDATA[<h3>Web3 User Experience Background:</h3><p>It is a well-known fact Web3 is clunky and lacks an easy or fluid User Experience(UX). However, there should be more discourse on the low re-engagement rate of existing Web3 users. I have already written about this in <a href="https://medium.com/@louis.moyn/why-web3-messaging-is-critical-for-all-of-web3-48213f28a740">a previous post</a>, but as a recap, if 100 new users enter Web3 this month, only 2.5 of them will re-engage next month. So it’s mostly us geeks who continue to go through the hoops of clunky Web3 user flows. In short, the current set of decentralized apps (dApps) is built for early adopters rather than late adopters.</p><p>Great front ends can only evolve if a solid foundational back end exists. For example, a Web3 wallet twelve-word seed phrase allows for self-custody and is secure, but there are better flows for mass adoption. A similar situation occurs when a blockchain asks for many authentications/signs every time we touch a blockchain. Multiple sign requests might offer solace to the early adopter geek, but this same user flow freaks out the late adopter, as it seems overdone and suspicious. Sometimes a different audience type interprets a feature polar oppositely from the original intent.</p><h3>Ethereum Updates:</h3><p>Ethereum launched ERC-4337 and Account Abstraction on March 1st, 2023 @ETHdenver. Ethereum is one of the most successful Layer 1 development platforms in Web3. Conversely, Bitcoin is a cryptocurrency designed for long-term investment holdings, akin to buying digital gold. Bitcoin founders had no intent to have a developer ecosystem build on top of its token (this is starting to change with Lightning Network but is still very early). Ethereum, on the other hand, has both its currency and a vast developer ecosystem where much more evolution has occurred in the last five years. Other blockchains are developer-focused too, but none as pervasive as Ethereum, so I will stick to the Ethereum example for now. Ethereum issued its whitepaper in 2013, and in most years since then, Ethereum has added functionality, features, updates, etc.; all are well <a href="https://ethereum.org/en/history/">summarized here</a>. ERC-4337 is one of those updates in March 2023 that speaks specifically to back-end improvements that should usher in better front-end UX &amp; UI. See more information on <a href="https://ethereum.org/en/roadmap/account-abstraction/#accordion-button-:R5j5alajkau:">ERC-4337 here</a>.</p><p>Ethereum was in the world for ten years before we had an update that specifically addressed UX, which suggests all the innovation up until now was very focused on back-end blockchain, cryptography, security, and ultimately community ownership. It was less about looking good and more about core capabilities which is entirely reasonable.</p><p>Until recently, wallets have transacted via Externally Owned Accounts(EOAs), and now there is a new way to transact under Smart Contract Wallets with significant front-end benefits. The full ERC-4337 spec can be<a href="https://eips.ethereum.org/EIPS/eip-4337"> found here</a>, but I summarized some back-end changes in the table below, with future front-end improvements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*mnJ3kzdzNmtAgOAw" /></figure><h3>Front End UX Timeline:</h3><p>This geeky ERC-4337 and Account Abstraction development in March 2023 paves the way for Web2-like onboarding, re-engagements, and account recovery. When will we see it improving the experience, and most importantly, when will we see higher re-engagement rates and lower attrition? Wallets and dApps could take at least three months to develop, three months to roll out, and another month to create a data set to measure improvements. Nevertheless, by Q4 2023, we should witness a significant step change in Web3 user health metrics.</p><h3>What does this mean for Web3 Messaging?</h3><ul><li>Web3 messaging protocols, as listed in <a href="https://medium.com/@louis.moyn/web3-messaging-part-2-7ca3f1a20da1">part 2 here</a>, have only been in production for the last year and are very early in their evolution. I don’t think we yet know who the winning protocols will be, but we should have some signs by the end of 2023</li><li>1: Many use cases are where Web3 messaging will find product market fit. Imagine a business sends a user an NFT notification, and the user buys a token from a button in the Web3 inbox, producing a much better experience for the user and higher conversion rates for the business (versus Twitter, Disscord &amp; email channels).</li><li>ERC-4337 will improve the generic user experience in Web3, creating fertile ground for more native Web3 conversations. More specifically, ERC-4337 Account Abstraction will make Web3 messaging action buttons much easier to a) code &amp; b) adopt.</li></ul><h3>ERC-4337 Applied to Layer 1 &amp; Layer 2&#39;s:</h3><p>Ethereum is an L1 Blockchain, but ERC-4337 will also apply to L2s such as Polygon, Arbitrum, and Optimism. It will be interesting to see which blockchain(L1 or L2) deploys a better UX first. For example, the <a href="https://www.lens.xyz/">Lens protocol</a> is built on <a href="https://polygon.technology/">Polygon</a> and deployed interoperable Web3 messaging (with <a href="https://xmtp.org/">XMTP’s</a> help). So I hope the Lens protocol via Polygon will utilize ERC-4337 soon too, which should bode well for Web3 social adoption.</p><h3>Outside of Ethereum’s ecosystem:</h3><p>I closely monitor the <a href="https://solanamobile.com/">Solana Phone</a>, which has a hard wallet and Web3 messaging from <a href="https://www.dialect.to/">Dialect</a>. ERC-4337 has no consequence to the Solana blockchain, but I see Solana Phone offering massive improvements to user experience, including Web3 messaging. Will Web3 hardware (Solana phone) or Web3 software (Ethereum 4337) usher in a better user experience? Predicting exact outcomes is difficult, but whoever substantially improves the UX first will be rewarded by user retention and, eventually, user growth.</p><h3>Who will deploy better UX and win more user adoption?</h3><p>Blockchains are the critical back end, and Wallets and Vertical dApps have been the front end to date in Web3. I think there are two ways this could transpire:</p><p>A. Wallets will own the user experience and user adoption or</p><p>B. Vertical dApps will own the user experience and user adoption</p><h4>A. Wallets UX:</h4><p>To date, wallets have been mandated by their respective blockchains to prioritize decentralization &amp; self custody over user experience because necessity is the mother of invention. But we have an outstanding question: “Can wallets pivot to a better UX now that ERC-4337 makes it possible?” Here is a <a href="https://blog.kyros.ventures/2022/08/18/an-overview-of-web3-wallet/">deep dive into wallet markets </a>for more background. Considering the UX has been so poor to date, I think it fair to say wallets that develop a better UX have an opportunity to gain market share… it’s there’s to lose.</p><h4>B. Vertical dApp UX:</h4><p>Web3 does not have its first billion users yet, because there isn’t yet an “iPhone moment” or “killer app” to attract and retain the first billion users. Web3 is sitting at 100m users, and wallets and blockchains may not get us there, considering the anemic 2.5% re-engagement rate. It might take a new mass consumer app to drive mass appeal, such as:</p><ul><li>Decentralized social media protocols like Lens or Farcaster</li><li>Decentralized Gaming apps akin to “The Fortnite of Web3.”</li><li>Decentralized shopping apps akin to “The Amazon of Web3.”</li></ul><p>I predict that Web3 Social will win 100 million recurring users before a wallet will, and wallets have many years of a head start. This belief is predicated on the viral behavior of social networks. Just because your friend buys and sells cryptocurrencies via a wallet doesn’t mean a network effect will emerge and extend the same behavior to your friend’s full social circle. In contrast, if a new social network were to appear (Web2 or Web3), it would require some network effects to succeed; essentially, Social is a mass adoption vertical. Defi is a critical early adopter vertical in Web3, but Defi is not a mass adoption vertical, at least not yet.</p><p>Vertical dApps could attract many more users than wallets, and if that were to transpire, you would see more vertical d’Apps developing wallets to improve user retention. For example, UniSwap, a leading decentralized exchange, just announced the <a href="https://uniswap.org/blog/uniswap-mobile-wallet-early-access">launch of its own wallet</a>. While Coinbase is a centralized exchange, they also launched their own wallet in 2022, offering credence to the idea that vertical dApps will disintermediate wallets if wallets don’t improve UX. Apple’s blocking of Uniswap’s wallet is a different problem to solve which is why the Solana Phone experiment is super interesting from an open ecosystem perspective.</p><h3>Bottom Line:</h3><p>ERC-4337 is an excellent advancement for Web3 UX and fertile ground for Web3 messaging regardless of potential competition between vertical dApps and Wallets. However, the advancement currently sits in the back end, and the front-end improvements will take longer to come to fruition. Those who deploy a better UX first will gain first mover advantage and others will follow any UX success. 2023 will be a great year for UX.</p><p>Please share any feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d644deddcd5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web3 Messaging (Part 2)]]></title>
            <link>https://medium.com/@louis.moyn/web3-messaging-part-2-7ca3f1a20da1?source=rss-17fef825e523------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ca3f1a20da1</guid>
            <category><![CDATA[web3-protocol]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[web3-adoption]]></category>
            <category><![CDATA[web3-messaging]]></category>
            <dc:creator><![CDATA[Louis Moynihan]]></dc:creator>
            <pubDate>Fri, 17 Feb 2023 04:48:49 GMT</pubDate>
            <atom:updated>2023-02-17T04:48:49.876Z</atom:updated>
            <content:encoded><![CDATA[<p>This is part two of a two part article, see <a href="https://medium.com/@louis.moyn/why-web3-messaging-is-critical-for-all-of-web3-48213f28a740">part 1 here</a>…..</p><h4>Quick recap from part 1:</h4><p>There are 100 million web3 wallets but only 2.5% are active monthly. This re-engagement rate does not bode well for the future of web3 so I proposed that as an industry, dApps should disclose DAU’s/MAU’s rates in order to improve the user experience and allow web3 to attract, re-engage its first billion users. Web3 users are required to wade across channel fragmentation in SMS, eMail, Telegram, Twitter &amp; Discord, all to accomplish a web3 use case like buying an NFT. There is no intuitive user journey to guide new users, hence the high attrition rates. I proposed, if a new web3 user was to use a web3 dApp with web3 conversations inside that dApp, time spent, re-engagement rates and therefore user experience would all be substantially improved.</p><h3>Part 2: Current state of web3 messaging</h3><p>I will cover the following topics:</p><ul><li>Basic components of web3 messaging</li><li>List of web3 messaging protocols</li><li>Problems to be solved</li><li>Examples of web3 messaging</li><li>Benefits of web3 messaging protocols</li><li>Outstanding questions &amp; areas of further review</li></ul><h3>Basic Components required for web3 messaging:</h3><p>The obvious components of web3 are a blockchain, a wallet, and a token to buy or sell.</p><p>The less obvious components for web3 messaging are:</p><ul><li>An identity that is easier to message than a random 26 character wallet address,</li><li>Cross chain and cross wallet integrations for large customer sets,</li><li>And of course, messaging protocols themselves.</li></ul><p>The diagram below provides a sample flow where web3 messaging protocol <a href="https://xmtp.org/">XMTP</a> works inside of web3 social dApp <a href="https://lenster.xyz/explore">Lenster</a>. You could imagine any dApp on any blockchain following a similar flow. Another example is messaging protocol “<a href="https://www.dialect.to/">Dialect</a>”, which works exclusively on the Solana blockchain. The top half of the diagram is mostly backend tech, and the bottom half of the diagram is mostly front end dApps, which hopefully will interface with web3’s first billion users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HpFyihq6Am_6yts_" /></figure><h3>List of web3 messaging protocols:</h3><ul><li><a href="https://xmtp.org/"><strong>XMTP</strong></a><strong> </strong>— Great progress on Lens protocol and web3 social messaging use cases</li><li><a href="https://www.dialect.to/"><strong>Dialect</strong></a><strong> </strong>— Great Progress on Solana, with on-chain buttons for better UX</li><li><a href="https://push.org/"><strong>PUSH</strong></a> — Great progress in one way notifications</li><li><a href="https://dispatch.co/"><strong>Dispatch</strong></a> — B2B and enterprise tooling in web3 messaging</li><li><a href="https://app.aardvark.sh/"><strong>Aardvark</strong></a> — Great UI for cross wallet messaging</li><li><a href="https://dm3.network/"><strong>DM3</strong> </a>— Cross-chain web3 messaging</li><li><a href="https://walletconnect.com/"><strong>WalletConnect</strong></a><strong> </strong>— Leader in cross chain, cross wallet integrations, and also building messaging protocols</li></ul><p>I will dig deeper into more web3 messaging protocols as their details become available.</p><h3>Problems to be solved in web3 messaging:</h3><p>It’s always good to make a clear distinction between the problems to be solved and the problems that don’t need fixing.</p><ul><li><strong>1:1 messaging</strong> is working really well in web2, users in N.America use iMessage to text friends and family and see no reason to download a distinct, new app to do that job. Internationally in regions like LATAM and APAC, users use apps like WeChat and WhatsApp for friends and family messaging. This problem has been solved. The counter argument is Apple and WhatsApp are centralized titans and users don’t own their own content or network. Honestly, IMO most users don’t care too much about this on Apple, Android or WhatsApp, but users do care about this problem in the category of Social Networking, which is why I believe we are seeing early progress with the Lens protocol. Social networking aside, 1:1 messaging is arguably a solved problem.</li><li><strong>1:Many Messaging</strong> for Web3 Use cases: There are many ways to broadcast messages in web2 using email, SMS, telegram, discord etc, but if a token creator in web3 wants to message the full community within web3, the 1:Many tools have been very limited until recently. We see this problem squarely being solved by all the web3 messaging protocols, but it’s only fair to call out <a href="https://push.org/">PUSH</a> as they are hyper focused on solving this specific problem.</li><li><strong>User Experience</strong>: Within web3 use cases generally, the user experience is very poor and disjointed (as previously discussed), especially as users are asked to authenticate (sign) transactions on the block chain over and over again. The explanations around these journeys are overly technical and just not intuitive enough for mass adoption. This is for sure a problem to be solved.</li></ul><p>I believe web2 use cases should stay in web2 channels. I don’t think we need new web3 apps that only allow for 1:1 messaging as that problem per above has already been solved by widely adopted apps.</p><p>In my opinion, the biggest problems to be solved today are:</p><p>1). Improving the user experience inside of web3 use cases,</p><p>2). Building native 1:Many messaging for web3 in a responsible way.</p><p>In <a href="https://medium.com/@louis.moyn/why-web3-messaging-is-critical-for-all-of-web3-48213f28a740">part 1</a>, I highlighted where eMail went wrong and why as an industry we need protocols for users to have controls over bad actors. It’s not enough to build protocols for 1:Many messaging, we will have to put controls in place to ensure it doesn’t become another spam channel.</p><h3>Examples of web3 messaging:</h3><p><strong>Example 1:</strong> In this first example of web3 messaging, I worked within the Lens Protocol and using my newly minted lens domain name “cognitio.lens” I joined a few web3 social networks, namely Lenster &amp; Orb. I created a few 2-way conversations in many web3 social apps and found that the Lens ecosystem (with the help of XMTP’s protocol) allows you to bring your messages to any dApp, making your messages and network interoperable.</p><p>Conclusion: Check out the same message showing up across all 3 dApps. This is NOT possible in web2 social networks. XMTP is the web3 messaging protocol being used by the Lens protocol and powering direct messages within Lens dApps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/986/0*509u92TEL6GNof7R" /></figure><p><strong>Example 2:</strong> While I wasn’t able to get beta access to Dialect, I am super intrigued by their approach. Dialect started on the Solana blockchain, which doesn’t sound great from an interoperability perspective but as I dove deeper into their features, it does seem like they have an advantage. Dialect’s “Smart messaging” makes it possible to send and receive tokens and interact with your favorite dApps right from your messages. This means, you could be inside a sports dApp and get a notification about a sports related NFT that you want to buy, and you can take action from the “buy” button in your sports dApp messaging inbox. This “button” functionality is a very basic feature in web2, but in web3 the comms functions have been completely separated from the on-chain transaction functions, and Dialect may have solved this massive UX issue on the Solana blockchain.</p><p>XMTP also has different content types that allow for action buttons, but similar to Dialect, I have not seen them in the wild yet, see button screenshots below from both XMTP &amp; Dialect. I would love to hear from the community how they see these buttons working in the wild.</p><p>Conclusion: The user experience is so much better with buttons in-thread, but the drawback might be interoperability as buttons that take action should not be transferable or actionable outside of the original context/surface. Dialect focusing on Solana might have been a better bet than I originally thought, as they might get more traction becoming a Solana standard with less competition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ry58RWWUuELcGPde4-mbLQ.png" /></figure><p>The benefits of web3 messaging are important to summarize:</p><ul><li>Ownership: The ability to own your own address, identity, network — not just the assets you purchase</li><li>Interoperability: where your identity, network and messages can be transferred wherever you want to go</li><li>Improved User Experience: specifically for web3 use cases</li></ul><p>The social dApps on Lens protocol scores really well on Ownership and Interoperability but smart messages(buttons) on Solana have got to be a better user experience, although I’d love to check it out for myself too.</p><h3>Outstanding Questions and areas of further review:</h3><ul><li>Is on-chain messaging better than off-chain messages, what are the pros and cons?</li><li>Do we have any proof points for web3 messaging benefits? Where’s the data, where are the case studies?</li><li>Are all the web3 messaging protocols collaborating or competing? While survival of the fittest method of selection will allow the best messaging protocols to rise to the top, I do wonder if there are some items that need more collaboration, such as user controls over bad actors?</li></ul><p>This concludes the series, but as you can see, we are very early in this protocol journey, and there is much more innovation to come. It will take time for successful and widely-adopted standards to emerge, and I would argue that the time is ripe to collaborate and help web3 messaging make all of web3 a more engaging surface.</p><p>Thank you to a few industry experts without their knowledge or input this would not have been possible: <a href="https://twitter.com/harshrajat">@harshrajat</a> <a href="https://twitter.com/aliquotchris">@aliquotchris</a> <a href="https://twitter.com/willwhite003">@willwhite003</a> <a href="https://twitter.com/shanemac">@ShaneMac</a> <a href="https://twitter.com/ttunguz">@ttunguz </a>and cheers for editorial help from <a href="https://www.linkedin.com/in/schutau/">Steve Chu</a> &amp; <a href="https://www.linkedin.com/in/alexisroucourt/">Alex Roucourt</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ca3f1a20da1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web3 Messaging (Part 1)]]></title>
            <link>https://medium.com/@louis.moyn/why-web3-messaging-is-critical-for-all-of-web3-48213f28a740?source=rss-17fef825e523------2</link>
            <guid isPermaLink="false">https://medium.com/p/48213f28a740</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[web3-messaging]]></category>
            <category><![CDATA[web3-communication]]></category>
            <category><![CDATA[whatsapp]]></category>
            <category><![CDATA[web3-protocol]]></category>
            <dc:creator><![CDATA[Louis Moynihan]]></dc:creator>
            <pubDate>Fri, 03 Feb 2023 21:22:55 GMT</pubDate>
            <atom:updated>2023-02-17T14:48:04.511Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I will outline why web3 messaging is critical for all of web3. <em>In Part 1, I will produce a retrospective on previous digital channels and compare them with web3 messaging foundations. In Part 2, I will explore the current web3 messaging foundations and what we can all do to attract our first billion users.</em></p><p><strong>Part 1. Digital Channel Retrospective</strong></p><p>Digital communication channels have only existed for forty years, yet the disruptions are profound. The internet is the largest communication advancement ever, but email specifically as a messaging channel completely disrupted the practice of handwriting a letter, placing a stamp on it and physically transporting to its pre-addressed destination (AKA: traditional post/mail).</p><p>Email was the first digital messaging channel disruptor, followed by SMS, Social Media and the current winners; messaging apps like WhatsApp, Telegram, WeChat etc. The evolution of digital messaging channels is based on each new dominating channel creating a step change improvement relative to the previous channels. Though, traditional mail still exists today, it has taken on a new context, as sending a handwritten note is now considered a huge act of care, but from an efficiency and productivity perspective, digital messaging channels have improved our lives exponentially.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dxZDWXLzdbi-rggcftHVCA.png" /></figure><p><strong>Disruptive Advantage of Each Channel:</strong></p><p>Email’s advantage over snail mail was a huge step change: you could send mail in minutes versus days, and productivity and efficiency soared both in personal and business use cases. Email was built on open protocols of POP, IMAP and SMTP, which allowed AOL, Yahoo, Hotmail to build user interfaces on those protocols and drive mass adoption to the point that all adult internet users typically have at least one email address today. However, email lacked effective anti-spam controls. Legislation was introduced as “C<a href="https://en.wikipedia.org/wiki/CAN-SPAM_Act_of_2003">an-Spam Act of 2003</a>”, but it was too little; too late as anti spam was not built into the technical protocols, it was very much an afterthought.</p><p>SMS’s disruptive advantage was not over email, but over phone calls. Local calls in most international countries had a cost and when SMS text messages were offered at a fraction of the cost of a phone call, network effects kicked in… and SMS 1:1 messaging took off. In the early days, users sometimes had to press a numeric button 3 times to select the correct letter, but this was a small UI/UX price to pay for more cost effectiveness and more efficiency.</p><p>Messaging app disruption offered free text and calling to users who downloaded a messaging app such as WhatsApp, WeChat, Telegram etc. SMS still had a cost associated and WhatsApp being free created massive economic benefits, especially in developing markets. Putting economics aside, all SMS users were limited to text, while WhatsApp innovated with richer features. Ultimately, WhatsApp produced a much better user experience and in some countries, citizens trusted WhatsApp and its end-to-end encryption more than their own governments. It is no wonder WhatsApp’s user base is heading towards 3 billion users.</p><p>Driving Question: How can web3 deliver another step change in digital communication channels and disrupt the dominant web2 messaging solutions of today?</p><p>Based on why and how previous channels were disrupted, I propose the next channel disruptor will need three main characteristics or pillars:</p><ol><li>Open Protocols</li><li>Identity &amp; Security</li><li>User Controls over bad actors</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/0*FYTBC6d6GB_EGbjO" /></figure><p><strong>Open Protocols:</strong></p><p>Email as a channel, proved that when the underlying protocols are open and available to all developers, mass adoption can be achieved. Web3 is very strong in this pillar as blockchain was built on open protocols by design, although the adoption of web3 messaging protocols is in its infancy.</p><p><strong>Security:</strong></p><p>Usernames and passwords are still used today in many digital channels, improved by adding 2 factor authentication. Web3 messaging already comes with the ability for encryption, which matches WhatsApp etc. Web3 is very strong in this pillar as wallet addresses authenticate to a blockchain and the auth is protected by a seed phrase. Layer 1 blockchains are prioritized on security too, and web3 is well designed in this pillar. Web3 like any new channel is challenged with bad actors, impersonators and user error but I do believe security foundations overall are strong and web3 has the ability to improve security even further.</p><p><strong>User Controls over Bad Actors:</strong></p><p>While there is some spam in WhatsApp, it is far less than the email channel so we can learn from WhatsApp in how they deal with bad actors. WhatsApp does not and cannot see encrypted messages between users, which makes it very difficult to police a user base of nearly 3 billion users and all the bad actors 3 billion users attract. Whatsapp handles this complexity by asking all recipients of net new conversations if they want to “block or continue” with each new conversation. While this is not a catch all, it has developed user behavior where reporting on bad actors is part of the overall process. While WhatsApp is centralized, WhatsApp encryption is decentralized, and the policing of bad actors has become more automated. Essentially, WhatsApp has messaging protocols to block users once they have exceeded a predetermined threshold of blocks. It is simple but effective.</p><p>How does web3 score based on the 3 pillars of Web2 disruption? In my opinion web3 is currently very strong in the first 2 pillars and very weak in the 3rd.</p><p>The underlying reason for this failure is mostly to do with very poor UI/UX and web3’s inability to re-engage its users. This is very easy to see when we look at re engagement rates across some of the more popular Web2 channels and compare it with web3 wallets. An industry standard way to measure this is looking at daily active users as a percentage of monthly active users, which is like asking the question: How many of your total users are engaged daily, see more details on <a href="https://www.klipfolio.com/metrics/saas/dau-mau-ratio/">MAU/DAU metric here</a>.</p><p>The first bar chart shows how incredibly successful WhatsApp is with its 2b+ users and how embryonic web3 user base is at 100m wallets. This reminds us how truly early we are and web3 is an incredibly small audience currently, and that’s ok.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/0*MiTEnc2pmQXEjVZ1" /></figure><p>The second bar chart is more concerning, you will see the engagement rate of WhatsApp is 70% while the engagement rate of web3 wallets is 5%. The industry standard engagement rate (DAU’s/MAU’s) is 20% and web3 is a long way off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/0*2YAEmyRqDjE1Etzp" /></figure><p>When 100 net new users onboard a wallet, only 5 users will return within a month, creating the biggest obstacle for web3 adoption in my opinion. Why is that the case? …because the user experience is fragmented and disjointed, do you remember when you first rubbed shoulders with a random 26-character wallet address, or when you had to use SMS, email, twitter and discord just to receive one pixelated NFT? This is pretty cool for early adopters but mass adoption will never happen under these experiences/circumstances.</p><p>Engagement rates are much higher on a 1:1 messaging app like Whatsapp versus an Airbnb app where an average user might only use the service a few times a year. Different verticals and use cases have different engagement benchmarks, so perhaps web3 messaging isn’t critical for all dApps but if our industry goal is to increase engagement in wallets and dApps generally, deploying web3 messaging is one plausible way to do so.</p><p>The industry needs to rally around our wallet re engagement problem, without fixing that, we just have an old fashioned leaky bucket where pouring more goodness in the top will just leak out the bottom of the bucket. Leaky Buckets won’t work regardless of whether it’s Web 1, 2 or 3.</p><p>Perhaps the way to ensure web3 has a fighting chance is to start measuring engagement rates inside dApps &amp; wallets and collaborate as an industry around this critical metric?</p><p>If you found my problem statement useful, please read <a href="https://medium.com/@louis.moyn/web3-messaging-part-2-7ca3f1a20da1">Part 2</a>, where I dive into web3 messaging solutions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48213f28a740" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>