Of the past several weeks, we have made some incredible progress, and are really exited to share with all of you. Each one is a major add-on to the existing RSS3 protocol, and will further help us build toward the world of Web3.

The Big Update

Starting from the beginning of the Internet, human beings have been creating assets online. Assets are not only about finance: all that you create or own in the cyber world are your assets. These started with simple contents on a self-hosted website, then went to more sophisticated datasets through different applications. Nowadays, with the advancement of decentralized infrastructures, we are seeing much more assets online like tokens and NFTs. We definitely are not going to stop there. If we take a look at the trend, it is easy to tell that the quantity and variety of online assets have been increasing for all the time being. Specifically, we expected to see more non-transferrable tokens and gaming assets in the next few years.

The next era belongs to the Metaverse, within which users will be creating more and heavier online assets through different applications, most likely on decentralized networks. The truth is that we cannot expect all assets to be on the same network. Or if they were on the same network, we cannot expect them to be of the same standards. Even for now, we see users with tokens on different chains with a majority on Ethereum, gaming NFTs like Axie Infinity on chains like Ronin, and articles and videos stored in a decentralized way on Arweave and IPFS. This is not determined by the users who always expect things to be simple, but by the underlying logic of these technologies that cannot be solved in a short time. Also, it might be better this way since it limits the harm of a possible, only in theory probably, single decentralized network failure (SDNF).

Assets' Interoperability across different applications will be achieved with much less effort this way. Right now, the way applications handle interoperability is by looking onto each chain, and searching for and verify the assets. If Metaverse applications are to handle as many cross-network assets as possible for better user experience and engagement, they will need a better way searching and verifying these assets. RSS3 files will be the trustless way for that, though we are still on our way of decentralization. To make things even easier, we will be introducing Web3 Pass as the simplest, the most adaptive, and the most powerful way for applications to use as trustless user profiles.

That major update restates the fundamental position of RSS3.

As a Cross-Network Aggregator

RSS3 is destined to become the indexer for any cyber persona, and we are adding verification and indexing modules to the protocol. RSS3Hub (or later the RSS3 nodes) will be able to verify ownership of given specific account, and then index the assets from verified accounts into the RSS3 files. And network does not only refer to decentralized networks, but also existing centralized platforms as well. Specifically, we are adding RSS3Account and RSS3Asset into the RSS3 Standard, and RSS3Hub will be first experimenting these new modules together with the introduction of the Web3 Pass™. We will soon release more information regarding the update and how community developers can easily implement these modules as well.

As a User-Controlled Index

It goes without saying that RSS3 does not stop with simply being an aggregator. If we look at the ways how users or addresses are showing their assets now, they are using the most primitive way. If you have 700 NFTs, then they will be displayed at once and the only options for the viewers are most likely to be pricing or chronology orders. The human touch is missing. And that's where RSS3 files come into play. With the enhanced RSS3Hub (which will later turn into RSS3 nodes), assets across different networks will be gathered, and for the first time in Web3 history, users are granted with the power to control this index. They can choose to show or hide any asset, and they are free to modify the order themselves. All your fans and friends will see your best collections, contents or achievements from your own index, in your own way.



When we first shipped out the RSS3 protocol, we designed it in a data-ownership first way, which requires a separate signature every time when the user makes a change. This is the simplest way for security, but definitely not good enough for social and content applications: they don't need to be confirmed for every action. So in this big update, we are introducing the new signing architecture called OneSign, which will completely change identity verification for non-financial dApps, making it more secure and convenient. And no, we haven't patented it lol and we want to call for all non-financial dApps, whether already adopting a similar architecture or not, to form an open standard called OneSign.

First of all, the private key for signing non-financial apps and financial apps should be different, eliminating possible security risks. At the same time, users should gradually form a conceptual model where different types of keys will be used for different cases.