# FAQ ### Why did Litentry rebrand to Heima? The rebranding marked Litentry’s evolution and renewed commitment to advancing **chain abstraction** and enabling **seamless interoperability** across diverse blockchain ecosystems. This rebranding was officially approved through Litentry’s decentralized governance process — see **Referendum #38**: . The new name marks a fresh chapter, signifying both technological evolution and community-driven progress. ### **Why choose the name “Heima”?** After much discussion and community input, we’ve chosen to rename Litentry to **Heima Network**. **“Heima”** means *“hometown”* — symbolizing a safe and welcoming place. It reflects our mission to provide users with **a stable, secure, and intuitive home for their digital identities and multi-chain assets**. Heima embodies our philosophy of: * Cross-chain integration * Seamless user experience * One-stop asset and identity management No matter which blockchain users are on, Heima is their **chain-agnostic home**. ### **What happens to the Season Program after rebranding?** The Season Program has been **paused for now**, but don’t worry, we haven’t forgotten the participants. All point collection and participation are **recorded on-chain**, and will be **taken into account** when designing new incentive mechanisms. Stay tuned! ### **When will $HEI staking launch?** **$HEI staking is planned for Q3 2025.** More details will be shared closer to launch. Make sure to follow our official channels for updates. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.heima.network/resources-more-about-heima/faq.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.