Web3 moves fast — new concepts or solutions seem to be hyped nearly every month. Some trends catch on — like L2s and NFTs, and some quickly sink into obscurity. A healthy distrust of the hype is good practice, but staying on top of things to understand the truly groundbreaking changes is essential, too. In this article, I’ll try to help you keep up by highlighting some of the current trends that I think have staying power: Account abstraction Composability Utility NFTs In-game assets for gaming Stealth addresses So, let’s check out these five current trends, what they mean for the ecosystem, and how you might leverage them! Web3 1. Account Abstraction (AA) could be the most significant Web3 trend of this year due to its potential to finally make onboarding to Web3 as simple as it is in Web2. Account abstraction Onboarding in Web3 is challenging because users need to install a crypto wallet, ensure they manage their keys securely, remember seed phrases, and acquire tokens to pay gas fees on their transactions. Compare that to entering your email or logging in with your social accounts in Web2, and it’s obvious why most users have yet to adopt decentralized apps (dApps). AA solves these issues by abstracting user accounts into smart contract accounts. Another way of thinking about this is that AA means every account is now a smart contract that can contain logic, user authentication, social recovery, etc. The typical activities we associate with a user account — signing transactions, for example — have been abstracted out. This allows for powerful functionality, such as the ability for a dApp to sponsor users’ gas fees and the ability to pay gas fees in any token. Many chains have chosen to implement--or are at least talking about implementing--AA. For example, (a popular wallet) uses AA with to implement multicall, where wallets can sign multiple transactions at once (instead of waiting for each one to complete). Argent X Starknet On , account abstraction is even broader and is the basis for Walletless Onboarding, which uses hybrid custody to create an onboarding experience for users that is nearly seamless. The hybrid custody model uses AA to allow for account delegation — where a child account delegates control to a parent account through a . This essentially allows one account to control another. Flow Capability This means: dApps can create wallets for users. There’s no key management, signing transactions, even knowing there is a blockchain behind the scenes. dApps can delegate access back to the user’s account when needed. dApp assets can be taken anywhere the user account goes — trading in marketplaces, etc. That’s a much better user experience than we see in most web3 dApps. 2. NFT and Smart Contract Composability Composability is the ability for developers to build on top of shared standards. It allows you to not only build solutions more quickly but also (since you are hopefully using open and proven solutions) to minimize risk. You could also say composability allows you to “ .” mix and match software components like LEGO bricks On , one example is that smart contracts are themselves building blocks. Your dApp or smart contract can call any existing smart contract and use its functionality as needed. You don’t have to rebuild basic functionality every time. Ethereum Another example is with NFT composability. As long as NFTs adhere to established standards, a wide variety of dApps can interact with them. The popular NFT , for example, to the Flow blockchain because the Flow architecture allowed for increased composability, even allowing NFTs to be equipped with other NFTs, such as purchasing NFT wearables for their Doodle. This also meant that NFT holders could take their Doodles to social, games, live events, and more. Doodles moved 3. Utility NFTs Most non-fungible tokens (NFTs) have no value other than the NFT itself (for example, generative art NFTs). For many people, this is enough! But more and more NFTs are starting to add utility — for example, token-gated services based on the NFT. An early example of this is ENS. If you buy an , you don’t just get the bragging rights of the NFT; you also get control over that ENS domain, including the ability to change its target address and metadata. As a result, an ENS NFT has a utility that goes beyond simple ownership. ENS domain , in general, are starting to add more real-world benefits and utility, and I expect more of the same in the future, for example: NFTs Subscriptions Access to events Certifications sharing Music royalties Access to music Metaverse ownership, such as land and fashion and much more as the tech evolves. 4. In-Game Assets for Gaming It’s been talked about for years, but are in-game assets for NFTs finally ready for prime time? Traditional games have had “token” economics for years. In-game currencies and assets are part of the business model, and achievements are strategically placed to keep players playing (think loot boxes). But in these traditional systems, players can’t transfer or sell their assets outside of the originating game. And if the company or game shuts down, your assets are lost. Blockchain-based in-game assets allow you to keep, control, sell, buy, and use these assets across games. If your fabulous ax in were an NFT, you could use it in other games that supported NFTs. If your Fortnite V-Bucks become tradable on a decentralized exchange for USDC, you could cash out whenever you wanted. World of Warcraft There are already: lots of in-game NFTs Metaverse land, such as The Sandbox God’s Unchained Cards Axie Infinity Axies In-game wearables in Decentraland So far, in-game NFTs have seen success in the play-to-earn space. Will we see it expand to interoperability? Will we see more popular gaming companies adopt NFTs? We’ll see! 5. Stealth Addresses Privacy is another hot issue on the blockchain. On most blockchain networks, transactions are public. If someone sends you tokens or an NFT, anyone can see the transaction and see the details — how much, the sender, the recipient, etc. While this is great for transparency, most users don’t want the world to know the details of their transactions. Stealth addresses solve this issue by providing transaction privacy. They allow you to automatically create a new address for each transaction. These new addresses are tied to your main address, but that link is only revealed to the parties in the transaction. Outside observers are unable to see the details of the link. So they can see the transaction, but they don’t know it’s associated with your account. This is important for adoption — if you were getting paid in crypto, for example, you wouldn’t want anyone to be able to see what your salary is. a system to bring stealth addresses to Ethereum. Vitalik Buterin recently proposed Blockchain privacy has also seen a regulatory crackdown recently (see the ). And in some instances, this is for good reason. We’ll have to see where privacy goes from here, but stealth addresses are on an interesting path! Tornado Cash issue Conclusion Those are five current that could be truly transformative over the next year. The space changes and advances quickly, though, so the best way to be early to trends is to stay involved, keep learning, and try out everything! Web3 trends Have a really great day! Also published . here

This story contains new, firsthand information uncovered by the writer.

Build an NFT Website Using The Flow Blockchain and Cadence [Part 1]

How to Improve Customer-Facing App Quality Using Tricentis' Testim

I ♥ writing code. Find me on GitLab.

Nominated for 2022 - HackerNoon Contributor of the Year - Javascript

Nominated for 2022 - Hackernoons Tech Storyteller of the Year

Nominated for 2022 - HackerNoon Contributor of the Year - Cloud Computing

Nominated for 2022 - HackerNoon Contributor of the Year - Heroku

Nominated for 2022 - HackerNoon Contributor of the Year - Design

Nominated for 2022 - HackerNoon Contributor of the Year - Salesforce

Too Long; Didn't Read

5 Web3 Trends That I'm Keeping an Eye on for the Rest of 2023

5 Web3 Trends That I'm Keeping an Eye on for the Rest of 2023

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

5 Signs You’ve Built a Secretly Bad Architecture (And How to Fix It)

Abstraction Layers and API's for Cloud Native Environments

Associative Links Explained

Code simplicity: A language independent perspective

Does Golang Follow the Object Oriented Programming Paradigm?

Navigating Apache APISIX: A Strategic Approach to Plugin Priorities and Execution Phases

5 Signs You’ve Built a Secretly Bad Architecture (And How to Fix It)

Abstraction Layers and API's for Cloud Native Environments

Associative Links Explained

Code simplicity: A language independent perspective

Does Golang Follow the Object Oriented Programming Paradigm?

Navigating Apache APISIX: A Strategic Approach to Plugin Priorities and Execution Phases

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps