Developer Hub
Relation ProtocolRelation ONE APIRelation Graph API
English
English
  • Overview
  • QUICK START
    • Deploy a Semantic SBT contract leveraging Relation Protocol
    • Deploying query services using Graph Indexer
  • KEY CONCEPTS
    • RDF
    • Semantic SBTs
    • Social Graph
  • Architecture
  • Schema Standard
    • Overview
    • How schemas limit smart contracts
    • Store schema
    • List of schemas
  • Contract Open Standard
    • Overview
    • Identity
      • Name Service
    • Relationship
      • Follow
      • Dao
    • Publication
      • Content
      • Privacy Content
  • Open Standard API
    • Introduction
    • EIP-6239
    • Business Interface
      • Identity
      • Relationship
      • Publication
  • Graph Indexer
    • Definition and usage
    • Listen to events
    • To parse RDF data
    • To build a social graph
  • Integrations
    • Quick start
    • Construct a social graph with Relation Protocol
    • List of resources
    • NameService contract guide
    • Follow contract guide
    • Dao contract guide
    • Content contract guide
    • PrivacyContent contract guide
  • Relation Name Service
    • Name Service Api
  • Use Case
  • APPENDIX
    • Deploy a contract using Hardhat
    • SemanticSBT Deployment tool
Powered by GitBook
On this page
  1. Contract Open Standard

Overview

Last updated 2 years ago

The Contract Open Standard is a smart contract specification defined by the Relation Protocol. It has two basic requirements:

  • The contracts should conform to the data format and interface specification defined by the .

  • The RDF data constructed by these contracts should conform to the .

Relation Protocol defined a set of Base Contracts based on the Contract Open Standard to address the three following scenarios.

Identity: Describe users' identity via SBT contracts.

  • Name Service contract

Relationships: Describe connections between different users via SBT contracts.

  • Follow

  • DAO

Publication: Describe users' public or privacy content published via SBT contracts.

  • Content

  • Privacy Content

Open Standard API
Schema Standard
Figure 5-1 Base Contracts