# Whitepaper Vol 1.3 * **v1.0 (March 2024)** – Original concept linking token to lithium reserves. * **v1.1 (July 2025)** – Updated to reflect speculative-token model with MiCA-compliant disclaimers. Removed asset-link references. * • v1.2 (July 2025) – MiCA Articles 4, 5, and 6-compliant crypto-asset description added. Finalized for regulatory notification and public release. * v1.3 (August 2025) – Tokenomics section fully updated to reflect CEX-only sale and incentive distribution. Investor Benefits section refined for clarity and MiCA compliance. Whitepaper finalized for public release with updated regulatory-aligned disclosures. * The LitiumLIC Project is a speculative cryptocurrency initiative built on the Binance Smart Chain (BEP-20). While the project was initially inspired by the concept of linking token value to lithium-rich land in Finland, the current LIC token holds no intrinsic or asset-backed value. LIC is designed as a utility-style crypto-asset that may evolve over time based on community interest, regulatory developments, and potential partnerships in the lithium industry. As demand for lithium continues to grow globally—particularly driven by electric vehicles (EVs), battery storage, and renewable technologies—LitiumLIC seeks to position itself as a forward-looking digital asset exploring future value integration opportunities. LIC does not represent ownership of any physical asset, security, or corporate right. Participation is entirely voluntary and speculative in nature. --- # 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://litiumlic.gitbook.io/whitepaper/readme.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.