It’s well known that Web2 giants typically sell user data to advertisers and have been mired in controversy for their approach to content moderation. And he biggest different between Web2 and Web3 is user’s privacy and identity.. Web3 proponents think they can build a new system altogether that sidesteps the concentrated power of platforms — a decentralized social media (DeSo) ecosystem where users ideally have more ownership over the content they create.

Getaverse DID and SBT will give users full control of their data and record their identity, and ultimately ensure their freedom through an open & censorship-resistant network. Getaverse’s vision is to help Web3 developers design better products by building a DID (Decentralized Identity) and a Reputation System for Web3 and Metaverse portals. Building a true decentralized society — DeSo (Decentralized Society) that allows users to control their identity, emphasizes ownership of digital content, and ensures that users receive value.

This article will try to narrate how Getaverse to utilize DID & SBT to achieve the goal of blockchain credit system.

DID is a derivative of the traditional centralized identity. It refers to the removal of ownership, control, and management of a person’s or company’s digital identity. User data is fully returned to the user.

DID places more emphasis on decentralization and peer-to-peer interaction among individual users in the identity system through identifiers. There is no single individual or group of trusted authentication nodes that can control the data generated. In this sense, DID focuses more on technical implementation and system architecture.

In addition, DID requires that all aspects of the identity system architecture be decentralized. Processes such as data storage, verification, and transaction are handled on the blockchain or distributed ledger to achieve complete decentralization, from the underlying protocol to the top layer of the application.

1.1 Authentication

Personal data assets are more easily forged or tampered with. Usually, data providers have strong motivation to fake or tamper with the data asset they hold. It can get more profits by performing such malicious behaviors. To defend against this, the data authentication needs to verify the authenticity of the data.Before the verification, Getaverse would define the authenticity of data. For web2 personal data, we find that most of them are produced by some applications. For example, the communication data is from Facebook or other social applications, the shopping data is produced in Amazon or other purchasing applications. Based on this observation, currently, we define the data authenticity as “whether the data is produced by a specific application”.

To verify the data authenticity, Getaverse will provide specific authentication functions. These functions compare the data provider’s data with the one downloaded from the corresponding application server (e.g., the Facebook). To achieve this goal, when a data provider sends a request to a verifier node, the provider should allow the verifier node to access its application account via secured authorization (such as OAuth2).

Meanwhile, Getaverse also allows the operator (external authorized agent) to valid the authenticity via Trusted Verifier Node. For example, considering an operator who wants to collect pictures of individuals’ portraits, the operator can implement an authentication function to detect whether the uploaded data is an image of a person’s portrait.

1.2 Digital Identity Evolution

Getaverse will build Credit Score System and Verifiable Claim Specification to protect user’s data and privacy in utilization.

Credit Score System is based on a user’s social account information and multi-linked address information. It applies blockchain technologies to build a reliable credibility assessment technology system to guarantee the openness and transparency of information, traceability and immutability, and establish a “trust” network. The technologies used include a series of complex mathematical algorithms such as hash encryption algorithm, timestamp, consensus mechanism, smart contract, etc.. Transaction participants do not need to know who is the target of the transaction, nor do they need to use third-party institutions to endorse or guarantee the verification of the transaction. Instead, they only need to trust Getaverse technical system, and create credit and consensus for the members of society through mathematical algorithms.

Verifiable Claim Specification is the subset of GraphQL that only allow aggregation queries to the encrypted data. A “Verifiable Claims” is a trusted assertion an issuer makes about an subject to an Inspector-verifier who is authorized to request such n. More specifically, it is machine-readable statement made by an entity that is Cryptographically authentic (non-Repudiation). A “credential” (aka attestation) is defined to be a set of Verifiable Claimss that refer to a qualification, achievement, personal quality, aspect of an subject such as a name, Government Identity, preferred Payment Processor, home address, or university degree typically used to indicate suitability.

The SBT token is programmable, non-transferable, but revocable and retrievable with verifiable information.

In the Web3 world, a user’s address, which can be considered a soul, stores SBTs (soul-bound tokens) that are corresponding to a set of affiliations, memberships, and certificates.A person’s “soul” (address) can store SBTs (soul-bound tokens) of educational certificates, companies they have worked for, artworks they have created, or books. The simplest form of these SBTs is the ability to “self-authenticate.” For example, by identifying the address as the founder of a Web3 dApp, it can verify him or her being a major artist in the art world.

2.1 Web3 Portal

With the nature of SBT, users will always have the freedom to move their social identity between applications without any tedious migrations or barriers, and developers will always have the freedom to build applications with new features on the network. And user’s on-chain & off-chain interactions would be recorded at Getaverse network, which will also give users relative tags as in other Web3 projects.

For Web3 Users: Soulbound Tokens grant users reputation tags to represent users contribution for projects. These tags are non-transferable and would follow user forever. And users don’t need to create so many accounts/addresses, they could log in and interact with projects through Getaverse in one-stop.

For Web3 Projects: Projects could utilize the tags to analyze & develop products and launch more effective marketing such as airdrop.

2.2 Certificate of Reputation

Getaverse supports verification of individuals by Getaverse Trusted Verifier Nodes, including centralized identities into the Getaverse DID system. Getaverse enables the management and data analysis of complex social activities by applying SBTs. It would create clear and segmented user profiles, such as “Uniswap Super Trader”, “Compound Lender”, “OpenSea Artists”, “Bored Ape Holder”, etc. These personal reputation is based on user’s on-chain interactions with projects and would be certificated by Getaverse according to Proof of xxx (work, activity, skill, etc), which give user a sense of honour and enable the project to obtain a more accurate user portrait.

Getaverse DID and SBT are mutually reinforcing for the Web3. The Getaverse team believes that with the development of Web3 and metaverse, the DID digital identity will become the most important Web3 portal in the future. It will not only greatly enhance the business value of Web3 and metaverse but also provide an important window for mapping reality in the virtual world.

Getaverse Official Links

Website: https://getaverses.com/

Twitter: https://twitter.com/GetaverseGlobal

Telegram: https://t.me/Getaverse_Official

Discord: https://discord.gg/MKe3YJyQ65

Medium: https://medium.com/@GetaverseGlobal

YouTube: https://www.youtube.com/@getaverse

GitBook: https://docs.getaverses.com/

It’s well known that Web2 giants typically sell user data to advertisers and have been mired in controversy for their approach to content moderation. And he biggest different between Web2 and Web3 is user’s privacy and identity.. Web3 proponents think they can build a new system altogether that sidesteps the concentrated power of platforms — a decentralized social media (DeSo) ecosystem where users ideally have more ownership over the content they create.

Getaverse DID and SBT will give users full control of their data and record their identity, and ultimately ensure their freedom through an open & censorship-resistant network. Getaverse’s vision is to help Web3 developers design better products by building a DID (Decentralized Identity) and a Reputation System for Web3 and Metaverse portals. Building a true decentralized society — DeSo (Decentralized Society) that allows users to control their identity, emphasizes ownership of digital content, and ensures that users receive value.

This article will try to narrate how Getaverse to utilize DID & SBT to achieve the goal of blockchain credit system.

DID is a derivative of the traditional centralized identity. It refers to the removal of ownership, control, and management of a person’s or company’s digital identity. User data is fully returned to the user.

DID places more emphasis on decentralization and peer-to-peer interaction among individual users in the identity system through identifiers. There is no single individual or group of trusted authentication nodes that can control the data generated. In this sense, DID focuses more on technical implementation and system architecture.

In addition, DID requires that all aspects of the identity system architecture be decentralized. Processes such as data storage, verification, and transaction are handled on the blockchain or distributed ledger to achieve complete decentralization, from the underlying protocol to the top layer of the application.

1.1 Authentication

Personal data assets are more easily forged or tampered with. Usually, data providers have strong motivation to fake or tamper with the data asset they hold. It can get more profits by performing such malicious behaviors. To defend against this, the data authentication needs to verify the authenticity of the data.Before the verification, Getaverse would define the authenticity of data. For web2 personal data, we find that most of them are produced by some applications. For example, the communication data is from Facebook or other social applications, the shopping data is produced in Amazon or other purchasing applications. Based on this observation, currently, we define the data authenticity as “whether the data is produced by a specific application”.

To verify the data authenticity, Getaverse will provide specific authentication functions. These functions compare the data provider’s data with the one downloaded from the corresponding application server (e.g., the Facebook). To achieve this goal, when a data provider sends a request to a verifier node, the provider should allow the verifier node to access its application account via secured authorization (such as OAuth2).

Meanwhile, Getaverse also allows the operator (external authorized agent) to valid the authenticity via Trusted Verifier Node. For example, considering an operator who wants to collect pictures of individuals’ portraits, the operator can implement an authentication function to detect whether the uploaded data is an image of a person’s portrait.

1.2 Digital Identity Evolution

Getaverse will build Credit Score System and Verifiable Claim Specification to protect user’s data and privacy in utilization.

Credit Score System is based on a user’s social account information and multi-linked address information. It applies blockchain technologies to build a reliable credibility assessment technology system to guarantee the openness and transparency of information, traceability and immutability, and establish a “trust” network. The technologies used include a series of complex mathematical algorithms such as hash encryption algorithm, timestamp, consensus mechanism, smart contract, etc.. Transaction participants do not need to know who is the target of the transaction, nor do they need to use third-party institutions to endorse or guarantee the verification of the transaction. Instead, they only need to trust Getaverse technical system, and create credit and consensus for the members of society through mathematical algorithms.

Verifiable Claim Specification is the subset of GraphQL that only allow aggregation queries to the encrypted data. A “Verifiable Claims” is a trusted assertion an issuer makes about an subject to an Inspector-verifier who is authorized to request such n. More specifically, it is machine-readable statement made by an entity that is Cryptographically authentic (non-Repudiation). A “credential” (aka attestation) is defined to be a set of Verifiable Claimss that refer to a qualification, achievement, personal quality, aspect of an subject such as a name, Government Identity, preferred Payment Processor, home address, or university degree typically used to indicate suitability.

The SBT token is programmable, non-transferable, but revocable and retrievable with verifiable information.

In the Web3 world, a user’s address, which can be considered a soul, stores SBTs (soul-bound tokens) that are corresponding to a set of affiliations, memberships, and certificates.A person’s “soul” (address) can store SBTs (soul-bound tokens) of educational certificates, companies they have worked for, artworks they have created, or books. The simplest form of these SBTs is the ability to “self-authenticate.” For example, by identifying the address as the founder of a Web3 dApp, it can verify him or her being a major artist in the art world.

2.1 Web3 Portal

With the nature of SBT, users will always have the freedom to move their social identity between applications without any tedious migrations or barriers, and developers will always have the freedom to build applications with new features on the network. And user’s on-chain & off-chain interactions would be recorded at Getaverse network, which will also give users relative tags as in other Web3 projects.

For Web3 Users: Soulbound Tokens grant users reputation tags to represent users contribution for projects. These tags are non-transferable and would follow user forever. And users don’t need to create so many accounts/addresses, they could log in and interact with projects through Getaverse in one-stop.

For Web3 Projects: Projects could utilize the tags to analyze & develop products and launch more effective marketing such as airdrop.

2.2 Certificate of Reputation

Getaverse supports verification of individuals by Getaverse Trusted Verifier Nodes, including centralized identities into the Getaverse DID system. Getaverse enables the management and data analysis of complex social activities by applying SBTs. It would create clear and segmented user profiles, such as “Uniswap Super Trader”, “Compound Lender”, “OpenSea Artists”, “Bored Ape Holder”, etc. These personal reputation is based on user’s on-chain interactions with projects and would be certificated by Getaverse according to Proof of xxx (work, activity, skill, etc), which give user a sense of honour and enable the project to obtain a more accurate user portrait.

Getaverse DID and SBT are mutually reinforcing for the Web3. The Getaverse team believes that with the development of Web3 and metaverse, the DID digital identity will become the most important Web3 portal in the future. It will not only greatly enhance the business value of Web3 and metaverse but also provide an important window for mapping reality in the virtual world.

Getaverse Official Links

Website: https://getaverses.com/

Twitter: https://twitter.com/GetaverseGlobal

Telegram: https://t.me/Getaverse_Official

Discord: https://discord.gg/MKe3YJyQ65

Medium: https://medium.com/@GetaverseGlobal

YouTube: https://www.youtube.com/@getaverse

GitBook: https://docs.getaverses.com/