> For the complete documentation index, see [llms.txt](https://metya.gitbook.io/metya/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metya.gitbook.io/metya/team-introduction.md). # Team Introduction Allen Soc — CEO Former Board Member at JP Morgan and Senior Executive at Uniswap Ventures, with extensive experience in investment and decentralized finance. He has overseen projects with a cumulative fund volume exceeding $10 billion. Christy — COO Led multiple high‑profile M\&A of global internet product companies, each exceeding $1B valuation. Brings deep expertise in product operations, corporate management, and M\&A strategy. Matthew Cole — CTO Former CTO at Uniswap; led multiple public‑chain tech upgrades in 2024 for crypto trading and smart contracts. Deep blockchain and crypto engineering background. Thomas Joseph — CLO J.D., Georgetown University; decades of experience guiding companies from venture to IPO. Successfully led several Nasdaq listings with cumulative financing in the hundreds of millions. Christian Tarala — CMO Cornell graduate and serial founder (CEO/CMO). Previously at a well‑known Nasdaq‑listed online dating company. Brings extensive entrepreneurial and marketing experience to Metya. --- # 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://metya.gitbook.io/metya/team-introduction.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.