Crypto Page Whitepaper
  • Introduction
  • Disclaimers
  • Overview
    • Social media owned by the user
    • Project Description
    • Like... but better!
    • More than that!
  • Key modules
    • Interaction patterns
  • Technical aspects
    • Technologies used
    • Best practices
  • Page.Account
  • Page.Content
    • Page.Content ID
    • Arweave storage
    • Comments
    • Likes/Dislikes
    • Posts and comments burning
    • Transmission control
    • Metadata
    • Hidden posts and comments
    • Encrypted posts
    • Copyrights and reposts
  • Page.Token
    • Page.Token usage scenarios
    • Emission model
    • Content monetization
    • Calculation formulas for created tokens
    • Tips
    • Integration with DEX
    • Page.Token and Crosschain
  • Page.Community
    • Community Settings
    • Encrypted Communities
  • Page.SoulBound
  • Page.DAPP
  • Page.Mobile
  • Page.Messenger
  • Page.DAO
    • Supermoderator
  • Page.Treasury
  • Page.Marketplace
  • Page.Bank
  • Page.Registry
  • Page.Crosschain
    • Page.Crosschain.Root
    • Page.Сrosschain.Bridge
    • Page.Crosschain.Merkle
  • Page.SafeDeal
  • Page.Ads
  • Page.Identity
    • Verification via social networks
    • Verification via partners
    • CrossChain verification
    • Page.DAO and Page.Identity
  • Page.Future
  • Road Map
  • Links
Powered by GitBook
On this page
  1. Page.Identity

Verification via partners

Confirmation of the connection between the user's wallet and a real person using third-party services

PreviousVerification via social networksNextCrossChain verification

Last updated 2 years ago

Crypto.Page will work with various business partners from both Web3 and Web2 to integrate their identity verification solutions into the Crypto.Page verification solution. We are considering two areas of integration:

  • Using existing verifications (for example, ) which will allow the user to issue the verification status for any wallet automatically. In essence, this means that we will read publicly available and reliably verified information about the associations of public keys (wallets) of users, and use this information automatically to assign a verified status within the Crypto.Page ecosystem.

  • Integration with the business partners carrying out the full verification process - which will allow the user to go through the entire verification process through the partne's interface. In this case, the user will be asked to go through the verification process through a partner (such as Onfido, for example). We expect that this process may be chargeable.

We expect the first integrations for verification through partners to appear no earlier than the end of 2023.

Sybil from Uniswap