FAQ IdentityHub
This page discusses Frequently Asked Questions for the IdentityHub. Please do not hesitate to get in touch via discord when you're running into trouble.
Please also visit more detailed FAQ's for Litentry Protocol or Trusted Execution Enclaves.
Can Litentry see the accounts in my IdentityHub profile?
No, the sensitive relationships between the accounts are stored in the Trusted Execution Environment, which is only accessible when the private key of the identity owner is included in the request to open it. Currently, all the SGX nodes are under the control of Litentry, which minimizes the risk of attacks by malicious nodes. Litentry is actively working towards decentralization, and the eventual decentralization of the nodes is inevitable. Please also read TEE FAQ
What is a shielding key and how do I set my Shielding Key?
A shielding key is a cryptographic key pair that is generated randomly and protected by the user password. Its public key is used by the Litentry TEE worker to encrypt user-sensitive information when passing back the data. It is used to encrypt all the data in the communication between the user and the Litentry Parachain. The shielding key is generated in the user’s local environment and used isolate sensitive user data from the IDHub server and all other third parties. Overall, it is an extra layer of security on top of your main account, used exclusively to encrypt your data for transmission and ensure only you or the Enclaves can decrypt it. Set shielding key 1. Sign in with your Substrate or EVM wallet 2. Go to My Identity 3. Click on “Account is not protected by shielding key” 4. Dialog pops up 5. set your shielding key with a strong password
I'm receiving the UserShieldingKeyNotFound error. How do I reset my Shielding Key?
You should reset your shielding key if you have been using an older version of the IdentityHub or experience problems linking accounts to your identity. If you get a UserShieldingKeyNotFound error, please reset your shielding key. You can reset your shielding key by clicking on 'My Identity' in the lefthand side. -> Afterwards click the 'Account is protected by shielding key' -> Reset Shielding Key. Once successfully done, linking identities and generating credentials should work.
My wallet is not connecting when setting my main identifier, or displays an error.
When you are experiencing an error upon wallet selection make sure your wallet isn't rejecting your connection with the IDHub website. You will need to allow the website access manually from the wallet extension. If one doesn’t consent the connection at the start, your wallet extension won’t ask again and deny websites to connect in the future. Adjust this setting and allow connection in the settings of your wallet extension.
Metamask, or another wallet, is installed but i'm unable to connect with the IDHub?
The problem you’re experiencing could be due to conflicts between browser extensions like Metamask and other built-in wallets (e.g., Coinbase Wallet). To fix this, disable all wallets except Metamask, restart your browser, and then test Metamask again. Multiple wallets in the same browser can often cause these issues.
What is 'linking an identity' & how do I it?
Identity linking refers to the process of linking a Web2.0 or Web3 identity with their Litentry or Litmus parachain address. An identity graph records the sensitive relationships between the different accounts of a user. It is used for mapping the user’s aggregated identity through any of the associated crypto addresses. The IDHub aims to provide the tool to generate a trustless identity graph that can be used for generating verifiable identity data for Web3 products and services. Link an identity 1. Set shielding key (See above) 2. Go to My Identity 3. Click on Link accounts 4. For web3 accounts 5. Select substrate or evm account 6. Sign the challenge code with your account-to-be-linked 7. Sign the transaction with your main address 8. Link Discord (If you are unsuccessful during campaign launch, wait until traffic is less) 9. Link Twitter (If you are unsuccessful during campaign launch, wait until traffic is less)
I'm unable to link any web2 accounts to my identity (Discord, Twitter)
The linking of your twitter or discord address relies on web2 API connections. There is a limit to the amount of connections we can make with web2 platforms at any given time. During peak traffic of campaign launches we request you to try again later.
What are the next chains that you would like to be more present on?
Our protocol is designed to be EVM compatible, furthermore Identity Data and the format in which we issue identity data is ‘blockchain agnostic’. A verifiable credential is a human readable text format. See it as an official letter that contains all the necessary information to verify whether the content in the letter is true. Although we are using a parachain as a trust anchor to store our verifiable credential on any other dapp or protocol is able to use these credentials without the need to be present on the polkadot ecosystem. So we can basically integrate any type of data a blockchain data indexer can offer, be it avalanche, solana, or other L2’s.
How does the shielding key protect my data during processing and computation?
A shielding key is a 256-bit AES-GCM cryptographic key pair that is generated randomly and protected by the user password. Its public key is used by the litentry TEE worker to encrypt user sensitive information when passing back the data. It is an extra layer of security on top of your Substrate private key (Account) used exclusively to encrypt your data for transmission and ensure only you or the Enclaves can decrypt it.
How do I send my verifiable credential to a dApp or community?
Decentralised identity is in it's early stages and we need to see industry wide adoption of it's standards to reach a very user friendly experience. Currently we are exploring different options of transferring a credential or json format to the receiving project, community or verifier of the credential. We are exploring sending the credential from a wallet or offer custom integrations with partners.
Will the IDHub's credentials be used for KYC?
Litentry is currently not heavily focussed on Know Your Customer type of verifiable credentials. Litentry supports the development of pseudonymous economies where credential are sufficient to Trust Your Customer. We hope to unlock a greater equality of opportunity for everyone regardless of their personal backgrounds or characteristics.
What is a 'Profile' inside the IdentityHub?
A profile in the IdentityHub consists of a collection of credentials that show how well you match a certain 'profile'. These profiles can be used to measure community contributions, a users DeFi experience or other metrics. A profile can be measured by a single credential but also a series of weighted credentials that compose a score. A profile is our preferred way of offering communities the opportunity to find users that fit their desired 'profile'.
Last updated
