We are excited to announce that Relation has cooperated with Lit Protocol to integrate the decentralized access control into Semantic SBTs!
With decentralized access control provided by Lit Protocol, access to encrypted content is granted based on on-chain conditions set by the content owner. These conditions could include things like owning a certain NFT. The network provides signatures and decryption keys to users who meet the conditions, but no single node in the network has full custodianship of the private key, making the process decentralized.
To encrypt content, the content owner generates a symmetric key and distributes it as shares across Lit’s network. They then set rules for when and under what conditions the network should provision the symmetric key to users. When a user attempts to access the encrypted content, the network checks if they meet the conditions (by prompting them to sign a message with their wallet), and if they do, the decryption key is provisioned to the user so they can unlock the content.
Privacy-Preserving features developed by Lit Protocol make it possible for people to meet their demand for diverse social interactions while protecting privacy. Therefore, to help users build a personalized and privacy-preserving social network, Relation has utilized the Decentralized Access Control SDK provided by Lit Protocol to develop a privacy module in the Semantic SBT Protocol to achieve encryption and gated access to private content in Semantic metadata.
Moreover, Relation has created the SBT template with the privacy module in the Semantic SBT Mint Tools, with which developers can directly deploy Semantic SBT contracts with decentralized access control. As soon as a Semantic SBT contract has been deployed, whitelisted users will be able to claim their SBTs in the SBT Bazaar and sign in to access the encrypted content in the SBTs.
As Semantic SBT Mint Tools integrated with Lit Protocol become open for everyone to use, individuals and communities will be able to accurately manage and control their privacy settings based on their own social networks and interactions.
Thanks to the integration of Lit Protocol, Bundlr and Arweave, Relation is able to use Bundlr, a decentralized storage scaling platform that increases the number of transactions conducted on Arweave, to upload the encrypted metadata in SBTs to Arweave for permanent storage.
Thus, the Semantic Metadata in the SBTs is not only privacy protected with decentralized access control but also stored permanently on the chain, paving the way for broader, diversified and personalized applications of Semantic SBTs.
Here is the Demo of how to deploy Semantic SBT contracts with the privacy module in the Mint Tools and how to decrypt the Semantic SBTs in SBT Bazaar. The privacy module is built based on the decentralized access control SDK provided by Lit Protocol. Both Semantic SBT protocol and Mint Tools have finished the integration. Welcome to check!
Semantic SBTs are programmable NFTs (non-fungible tokens) that are metadata-linked and interconnected in a way that is machine understandable and interpretable. A semantic SBT is a new type of SBT with semantic meaning written in the metadata which represents a statement with three attributes including a subject, a predicate and an object.
The main difference between Semantic SBTs and other SBTs is that they are designed to provide a richer, more meaningful description of the data they represent. This is achieved by linking the SBTs to semantic ontologies, which define a set of concepts and their relationships, allowing machines to understand and interpret the relationships between different data sources.
In the context of building the Web3 Social Protocol, Semantic SBTs are used to provide a decentralized digital identity solution that is both self-sovereign and verifiable. By analyzing the social relations of individuals and communities in a decentralized way, Semantic SBTs can be used to represent proof not only of a person’s identity but also their friendships, affiliations, memberships, qualifications, and even employment on the blockchain.
These Semantic SBTs are then collected into what are called “Soulbound Journals” (SBJs), which list all the identifying information of the account through its constituent Semantic SBTs. SBJs provide proof of attendance, proof of skillset, and proof of personhood, and they can be used to protect against Sybil cyberattacks, target-market services based on user interests and needs, and help with social recovery wallets.
Overall, Semantic SBTs and SBTs are important tools for advancing the capabilities of Web3, providing a new paradigm of identification and verification that balances the need for trust with the precepts of decentralization and anonymity.
The integration of decentralized access control provided by Lit Protocol has created a privacy module in Semantic SBTs and will greatly expand the application scenarios of Semantic SBTs and its protocol in Web3 Social.
For example:
Gated Social Club
By setting the holding of a Semantic SBT with privacy module as a requirement, the access of members in a social club will be automatically managed with the SBT. Therefore, the Social Club will be more private and more flexible for managing Club members.
Access-Controlled Content
By setting certain requirements as conditions, only people who meet the requirements will be able to access the content to protect privacy, manage permissions and target audiences.
Quick Adoption for R&D
Since the Semantic SBT Protocol and Mint Tools have integrated the Lit Protocol, it will be very easy for developers to utilize and integrate. More Social Dapps and scenarios could be expected to spring up in the future!
The Integration between Lit Protocol and Relation has profound significance, especially for building a decentralized society. Semantic SBTs with the privacy module will open up more possibilities for Web3 Social which needs to meet various personalized social demands. By the way, Relation keeps trying to complete more innovative integrations to optimize Semantic SBTs and the Web3 Social Protocol.