> For the complete documentation index, see [llms.txt](https://docs.bullpen.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bullpen.fi/about-bullpen/what-is-bullpen/team.md). # Team We’ve lived crypto from every angle — trading, building, and scaling products for millions of users. Our team has shipped at **Hyperliquid, Deribit, Paxos, Galaxy, Zeta Markets, Kraken, and Berachain**, and now we’re building Bullpen to push the frontier of providing an on-chain trading CEX experience. **The founding team behind Bullpen includes:** * [**Sal Qadir**](https://x.com/salxyz)**, CEO** – Co-Founder of BullpenFi. Previously at Galaxy and ShapeShift. Host of *FullPort* (30k–120k weekly views) and *Unlayered Pod*. Computer Science, Cornell Tech. * [**Ansem**](https://x.com/blknoiz06)**, Co-Founder** – Prominent Solana advocate, market analyst, and community investor with a track record of driving ecosystem adoption and education. * [**Luca Spinazzola**](https://x.com/Luca_Spinazzola)**, Co-Founder & Head of Engineering** – Software engineer and multiple time founder. Experienced in native app development, web3 infrastructure, and open-source contributions. We started Bullpen to deliver the **speed of centralized exchanges** with the **transparency and community of DeFi**. First with perpetuals and Solana spot, and soon with the next generation of crypto-native markets (prediction). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bullpen.fi/about-bullpen/what-is-bullpen/team.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.