Connecting Identities and Credentials to Nplifier
Identity, Credentials, & Challenge Management is the core function of Nplifier. Through API Connectivity between Nplifier and users’ existing Web3 and Web2 services, users can link identities to Nplifier, and complete challenges to accumulate and combine credentials. Definitions and relationships among the three entities are provided below:
Identity: A logical entity used to identify a user on Web3 or Web2 applications. By default, the platform creates an Nplifier ID for each user. The Nplifier ID is associated with the user’s email (Web2) and a platform managed EVM address (Web3). The users can link any Web3 wallet addresses, email addresses, or user identifiers on other Web2 or Web3 applications to this identity. More importantly, they can select any of the identities they linked to interact with applications that use Nplifier identity services and to accumulate their credentials on- or off-chain.
Credential: A proof of achievement (PoA) associated with an identity. In Nplifier, a credential is a snapshot of a PoA and is also an index pointing to the entry in the Nplifier repository or a Web3 or Web2 application where the PoA associated with an identity is held. In the real world, some types of user’s credentials are permanent (e.g., academic certificates and degrees, presentations at conferences), while others are ephemeral (e.g., ownership of a specific NFT, EVM address has certain amounts of tokens). Therefore, Nplifier treats credentials as snapshots, and is equipped with capabilities to verify credentials dynamically with issuers and the Nplifier repository.
Challenge:In Nplifier, a challenge is a task to be completed by an owner of an identity to earn a credential. There is no boundary for challenge types, but a valid challenge can always be evaluated as either true or false (a.k.a. task completed or not). Currently, Nplifier supports four major types of challenges to cover empowerment scenarios in Web3, Web2, and Nplifier itself. First, for Web3, Nplifier supports standard ERC-20 and ERC-721 contract related challenges, for example, a challenge task could be “having at least a specific number of ERC-20 tokens” or “current ownership of a particular NFT.” Secondly, for Web2, Nplifier plans to support major social network services and corresponding credentials which may include verification like: "subscribes to a specific YouTube channel", "retweeted a Twitter post," or "ordered a specific product on an ecommerce site." Thirdly, any linked identity can be used in the Nplifier whitelist system. Finally, credentials accumulated in Nplifier can be used in challenges: taking challenges to join a club and participate in a campaign are two typical examples. In Nplifier, multiple challenges can be combined in a single qualification which evaluates multiple conditions. This enables campaign organizers to be granular and expressive. Learn more information about Qualification.
Based on relationships among Identities, Credentials, and Challenges, Nplifier can link and verify existing identities and credentials without replicating user data or trying to replace users’ favorite Web3 and Web2 services. If the users choose not to store their online data elsewhere on Nplifier, Nplifier reuses linked user identities and credentials for identity and credential verification purposes only, e.g., qualifying group memberships, voting qualification, taking specific actions on a specific social network, etc. On the other hand, Nplifier also provides users with an option to retrieve and store their online footprints (for online applications that Nplifier has already connected) securely in the users’ Private Data Vaults. Nplifier’s power comes from its consolidation of identities and credentials, and the open Nplifier APIs enable other services to connect back to Nplifier to build a “Credential-as-a-Service” world together.
Last updated