Technical Overview
The Relation Protocol's technical infrastructure is a comprehensive ecosystem leveraging state-of-the-art technologies to empower decentralized social graph management. It comprises four fundamental components: RDF, Semantic SBTs, Social Graph, and Scaling Solutions. Each of these elements is pivotal in supporting the protocol's functionality, scalability, and user-centric orientation. Collectively, these components form a robust and forward-thinking technical backbone for the Relation Protocol, enabling decentralized social graph management, promoting user control over data, and paving the way for a more inclusive, transparent, and user-centric social networking experience.
How the Relation Protocol Works
The Relation Protocol is architecting the decentralized social layer for Web3, offering chain-native social experiences that facilitate seamless data integration and customizable privacy settings. This framework enables communities to better coordinate within more open and inclusive, community-owned economies while enhancing user sovereignty and network effects.
The Relation Protocol integrates the Resource Description Framework (RDF), a flexible and expressive graph data model that succinctly describes relationships between resources. This framework is ideal for representing social graphs and other complex data structures. With RDF, the Relation Protocol simplifies the integration of data from multiple sources, representing it in a consistent and interoperable format. This framework offers a highly scalable and composable data model for social networks, enabling disparate applications and smart contracts to interact seamlessly and share data.
Therefore, the Relation Protocol empowers the decentralized social data middle layer for Web3. Multi-chain social data is integrated into the global social graph through the RDF. The private module, characterized by Private SBTs, for configuring privacy settings is a distinctive feature that grants users control over content access in various social contexts. The native on-chain storage by Semantic SBTs, or the publicly visible storage on Arweave, for data hosting eliminates the necessity for trusted intermediaries, thereby enhancing decentralization and security.
Relation Protocol’s Framework
Relation is meticulously constructing a comprehensive decentralized social networking framework comprising three essential layers: the base layer, the semantic layer, and the application layer. These layers are grounded in Relation's standardized framework, fostering an environment where developers can collaboratively shape the future of decentralized social connectivity.
A key element of Relation's methodology is its adherence to a standardized framework. EIP-6239 Semantic SBTs, proposed by Relation Labs, exemplify this commitment. They serve as a critical component within the structured data standard framework for social networking. By maintaining these standards, Relation ensures compatibility, interoperability, and future scalability of the decentralized social graph.
Relation champions an ecosystem where developers are inspired to leverage its standardized framework to contribute to the co-creation of decentralized social connectivity. The open and collaborative nature of Relation's ecosystem cultivates innovation, diversity, and the seamless integration of state-of-the-art technologies. Together, we're building a decentralized social landscape that empowers individuals, respects privacy, and enhances the way we connect and interact in the digital age.
RDF in Relation Protocol
The Resource Description Framework (RDF), an international standard published by W3C, is integral to the Relation Protocol. It represents knowledge in a structured manner using triples (subject, predicate, and object), forming the basis of RDF graphs. RDF Schema offers a data-modeling vocabulary, allowing for the definition of classes and properties, leading to structured data. Relation Protocol leverages RDF's ability to integrate and interconnect diverse data sources for a rich semantic network of relationships and knowledge discovery.
Semantic SBTs and their Role in the Relation Protocol
Semantic Soul Bound Tokens (SBTs) were introduced as a transformative force in the Web3 sphere to foster a personal identity system. SBTs can represent various facets of an individual's identity in an efficient and standardized manner using RDF triples. The Relation Protocol utilizes Semantic SBTs to monetize digital information, enabling the establishment of data ownership and trade history. The data generated by Semantic SBTs, marked by personal ownership, diversity, and continual generation, contributes to a valuable tech and business solution for personal identity systems in Web3.
Social Graph
The Social Graph in the Relation Protocol signifies a model of social networks, encapsulating social relationships among entities. It constitutes social data nestled within numerous Semantic SBTs in a graph database, providing a detailed portrayal of the social landscape within the Relation ecosystem.
Identity
Identity within the Relation Protocol encompasses a Relation Name Service and several Semantic SBTs describing the identity. This scalable design ensures all contracts adhering to the Contract Open Standard will have their RDF data parsed as a part of user identity, encouraging developers to contribute to the decentralized network's identity system.
Relationship
The Relation Protocol portrays relationships as social connections between entities, crucial in defining permissions. The protocol offers two predefined relationship scenarios: "Follow," marking social connections between users, and "DAO," denoting group relationships and DAO memberships.
Publication
The Publication module in the Relation Protocol is designed for creators to publish original content, whether text, images, or videos. It consists of public content visible to everyone and privacy content with customizable visibility settings.
Scenario Extension
The Relation Social Graph also supports scenario extensions. Developers can submit schemas adhering to certain standards to address scenarios not yet covered in the current social graph, thereby expanding the protocol's versatility.
Architecture
The Relation Labs Architecture is centered around the Relation Protocol, an open and decentralized social graph protocol. This facilitates the deployment of contracts and the creation of Dapps via the Semantic SBTs specification, ensuring standardized, machine-readable RDF data. The protocol places control and governance of data in users' hands, fostering a collective, blockchain-native social graph data layer.
The Architecture includes two core elements: components and deployment.
Components
The Relation Protocol comprises four key components:
Schema Standard: This standard defines the format for social data storage, dictating all social data formats built on the Relation protocol. It includes a Base Schema that all RDFs must conform to, managed and updated by the Relation DAO.
Contract Open Standard: This smart contract standard requires the contract to comply with the data format and interface specifications defined in the Open Standard API. Moreover, the RDF data built by the contract should conform to the Schema Standard.
Open Standard API: This API specification allows developers to access the Relation Protocol, forming the basis of the Contract Open Standard.
Graph Indexer: This parser standard indexes SBT data in the Relation Protocol, allowing anyone to deploy data monitoring services. It assembles SBT data in Ethereum and Arweave, constructing a Social Graph for use by social applications.
Deployment
Contracts within the Relation Protocol are deployed on the Ethereum network or L2. Semantic SBT contracts for specific scenarios can be deployed by social applications, or pre-designed and deployed contracts can be called upon.
The Schema in the Relation Protocol is comprised of TTL files stored on Arweave, constraining the RDF data specification of Semantic SBT contracts.
For privacy, Semantic SBTs use unique schemas and storage methods. The RDF data of privacy SBTs needs to be encrypted or decrypted using a privacy protocol (such as the Lit Protocol) before storage, allowing users to manage and control data accessibility.
Last updated
