> For the complete documentation index, see [llms.txt](https://flickrz.gitbook.io/whitepaper-flickrz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flickrz.gitbook.io/whitepaper-flickrz/key-team-members.md). # Key Team Members **The Flickrz CEO is** **Steve**, a founder of Flickrz and also the former founder and CEO of Toomics. Toomics is now one of the global top 5 webtoon platform, the company valuation has elevated from scratch to 160 Million USD at exit. Alongside with Steve, there is Ben and Mark, who co-founded Toomics, supporting the project in many ways. **Travis, the CTO**, is also from Toomics as a CTO. He’s made great contribution of the technical aspect of the project for Toomics to exit successfully with a 70 million user-base platform with 25 million MAU. Currently, he is in charge of all the tech side and product building for Flickrz, he’s leading the tech team and finalized the product development in terms of webapp, wallet integration, internal transaction structures so the service is ready and operational. --- # 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://flickrz.gitbook.io/whitepaper-flickrz/key-team-members.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.