FAQ Heima Network
Please feel free to ask any questions on our Telegram or Discord channels to help us refine this section with frequently asked question.
Please also visit more detailed FAQ's for the IdentityHub or Trusted Execution Enclaves.
What is the network token? LIT or HEI?
The network token for Heima is HEI token, since Heima netwrok evolve from Litentry, the LIT token is the predecessor of the HEI token. Currently most exchanges only support HEI token, and only HEI can be utilized on our network, if you have LIT token on Ethereum or BNB chain, please swap it to HEI on the swap portal
Why use L1 instead of L2
In general L1 provides superior security, customization, and governance autonomy, making it a better choice for projects that require deep protocol-level control and long-term sustainability. While L2s are excellent for scaling, they introduce dependencies on their underlying L1, limiting flexibility and security guarantees.
Being evolved from Litentry, a substrate-based L1 blockchain, Heima Network inherits its modularity, flexibility and security, which forms a solid ground for chain abstraction and cross-chain operations.
What is the chain abstraction?
Chain abstraction is a technology that simplifies and unifies interactions with multiple blockchain networks by hiding the underlying complexity of each individual chain. Instead of requiring users or applications to interact with different networks separately, chain abstraction provides a seamless interface where operations, such as asset transfers, identity verification, and data access, are managed efficiently without requiring knowledge of the underlying protocols.
with Heima network, chain abstraction allows:
Users: To manage and trade assets across multiple blockchains without switching wallets or manually handling cross-chain operations.
Developers: To build applications without worrying about the intricacies of integrating multiple blockchain networks.
Applications: To provide seamless multi-chain experiences, improving user convenience and expanding access to decentralized services.
Why did Heima start with Polkadot?
It let us to focus on the main function of our blockchain without thinking about the security.
There are a couple of reasons: the historical context is that back in the early days of our project, we were using Ethereum to build applications which heavily subject to transaction fees and long duration time. It wasn't a particularly good experience for both users and developers, so we started to look for alternative products. We believe that cross-chain will be the future of blockchain, and after comparing different projects ex. Cosmos, Polkadot, we decide to move forward with Polkadot.
Polkadot has fast iteration, cutting-edge technology, and high potential in the cross-chain space. It has a vision of helping people build entire blockchains and integrating these blockchains with each other. The CTO Gavin Wood also has a deep understanding of Web 3 and the blockchain application ecosystem. With Polkadot, we find it relatively easier and more efficient to build our protocol related to building from scratch.
How do you ensure privacy during the sharing of Identity Information?
Every interaction between the User's local environment & TEE gets encrypted with the Shielding Key.
Every verifiable credential gets encrypted with the public key of the receiver before transmission.
We lower the information resolution to boolean statements or ‘truth’ statements that only reveal the required necessary information without doxing the user. We issue proofs to statements without leaking the root information itself. E.g. user has an active wallet address that is older than 5 years.
Can Heima see the sensitive relationships between the accounts in my 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 Heima, which minimizes the risk of attacks by malicious nodes. Heima is actively working towards decentralization, and the eventual decentralization of the nodes is inevitable. Please also read the TEE FAQ
Last updated
Was this helpful?