> For the complete documentation index, see [llms.txt](https://lumi-vault.gitbook.io/lumi-vault-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lumi-vault.gitbook.io/lumi-vault-docs/lumi-vault-mining-business-model/team.md). # Team ### πŸ”Ή Core Team LumiVault is led by a seasoned team of professionals with decades of experience across mining, blockchain technology, exchange infrastructure, finance, and global markets. Their combined expertise ensures the successful execution of the project’s gold-backed digital asset strategy and its long-term vision. *** **CEO β€” Alexey Drozdov (Kazakhstan)** Alexey is a seasoned executive with two decades of experience in infrastructure development and natural resources. He began his career at **PSK TransStroy** in Moscow as Deputy General Director for Infrastructure Development (2005–2015), before moving into mining and exploration as Director of Exploration & Development at **Uguumur Alt LLC** in Mongolia (2016–2018). He later served as Strategic Advisor in the Natural Resources sector with **Yer-Tai LLP** in Kazakhstan (2018–2023). In 2025, Alexey became CEO of **LumiVault**, where he leads strategic growth, mining partnerships, and RWA-backed asset innovation.\ πŸ”— LinkedIn: *** *** **CMO β€” Anna Kowalska (Poland)** Anna brings 17 years of expertise in strategic marketing and brand leadership across Europe. She started at **EduSoft** as a Marketing Specialist (2008–2013), before advancing to **Bright Media** as Marketing Manager (2013–2018). She then joined **NextWave** as Senior Marketing Manager (2018–2023) and later served as Head of Marketing at **Nordic Creative** (2023–2024). In 2025, Anna became CMO of **LumiVault**, overseeing global marketing strategy, brand positioning, and ecosystem adoption.\ πŸ”— LinkedIn: *** #### **CTO β€” Dmitri Smirnov (Estonia)** Dmitri is a technology veteran with two decades of experience in software engineering and blockchain architecture. He began as a Software Engineer at **Tallinn Software House** (2004–2009), later becoming Lead Programmer at **Infinitum Interactive** (2009–2011). He contributed as Systems Engineer at the **Tallinn Open Source Initiative** (2012–2018), then worked as Senior Systems Architect at **ZA/UM** (2018–2021). Most recently, he served as Backend Developer at **MyCointainer** (2021–2024). In 2025, Dmitri joined **LumiVault** as CTO, where he leads technical infrastructure, on-chain proof-of-reserve development, and RWA integrations. *** #### **CSO β€” Miroslava PetrovΓ‘ (Czech Republic)** Miroslava is a strategy leader with deep expertise in fintech and blockchain ecosystems. She started her career at **PwC Czech Republic** as a Strategy Consultant (2008–2015), then joined **CoinMate.io** as Business Development Manager (2015–2019). She later held senior roles as Head of Strategy at **Kriptomat** (2019–2023) and Senior Systems Architect at **MyCointainer** (2023–2024). Since 2025, Miroslava has served as CSO of **LumiVault**, driving long-term business strategy, exchange partnerships, and adoption in the RWA sector. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://lumi-vault.gitbook.io/lumi-vault-docs/lumi-vault-mining-business-model/team.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.