The concept of data ownership has evolved with the emergence of Web3, which aims to return control over data to the users. However, in many cases, data generation occurs in a different context detached from the constraints of data generation. As such, giving users complete control over their data in a crude manner can be considered irresponsible. RIDO steps in to redefine the ownership of Web3 data, addressing these concerns and providing a more comprehensive and responsible solution.

In the journey to return data ownership to the user, there are three key benefits that can be realized:

1. Application parties cannot arbitrarily delete or modify user data.

2. User data can be used across applications.

3. Users can monetize their money

However, it is crucial to note that giving users complete control over data ownership does not always guarantee benefits 2 and 3. For instance, in the game League of Legends, a user's gaming record and level are considered personal data. If a user is given total control over this data and can freely modify it, the applications cannot trust or use this data, nor can it be utilized across different applications or for data monetization.

Ownership, structure, and context of data are closely related in RIOD.

Firstly, RIDO introduces programmable data generation, a mechanism that requires any party defining the data structure to also define the conditions for modifying the data. This approach ensures that data ownership is managed more responsibly, without compromising the integrity and usability of the data.

Programmable data generation limits the power of owners and makes users' data more valuable. ****For example, a DID that defines a variable profile with a field called eth_address representing an EOA would require the owner of the variable profile to provide the corresponding signature when modifying the value of eth_address.

Additionally, RIDO also supports programmable access control, enabling users to set arbitrary access control functions. When certain conditions are met, users gain access control permissions. For example, users can set access control such that any user holding a BAYC NFT can access their "age" information.

DA Layer

The DA layer is responsible for data storage. Dynamic data is stored in IC contracts, while static data can be encrypted and stored by users using IPFS, Arweave, BNB Green Field, S3, and other options. The RIDO protocol in the logic layer helps users build indexes, manage files, and control access.

Logic Layer

The logic layer is the core of RIDO, where users can build abstract logic, including defining variable structures, defining access control permissions, managing static data in the DA layer, and compatibility with DID. Data generation conditions and access control conditions are implemented in this layer.

DID and Routine

Each data space has a controller, which can be any DID. Currently, the space accepts different public chain wallets such as IC Wallet, Metamask, and Martin for direct control. In the future, more Web3 and Web2 DID systems will be supported. RIDO will support various DID systems such as address and ENS for addressing and message routing through different DID methods.

With RIDO, the possibilities are endless. So, unleash your imagination and contribute to the future of data ownership.

Website: https://www.rido.io/

Twitter: https://twitter.com/rido_crypto