> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/exchange-layer-1/overview/contributors-and-partners.md). # Contributors & partners ## Team The Nexus team has expertise in financial markets, AI, and large-scale systems engineering. Team members studied at Stanford, UC Berkeley, UCLA, University College London, and Brown, and have worked at technology and finance organizations including Google, Amazon, Microsoft, PwC, and Mozilla. ## Advisors Nexus's advisors include cryptographers and leaders from institutions such as NYU, MIT, Harvard, UC Berkeley, and Cornell, and from the Ethereum Foundation, Zcash, Chainlink, and Bitso. ## Investors Nexus's investors are led by Dragonfly, Lightspeed, and Pantera, and include Faction, SV Angel, Alliance, Blockchain Builders Fund, and the Stanford Blockchain Accelerator. ## Technology & protocol partners * **M0** is collaborating on [USDX](https://docs.nexus.xyz/usdx), the dollar unit the Exchange accounts in. * **Hyperlane** provides cross-chain [bridging](/exchange-layer-1/nex-token/tokens-and-bridges/bridging.md) for NEX between Ethereum and BSC. ## Build on the Exchange The Exchange is API-first, so any team can build on it through the same REST and WebSocket API the Nexus UI, SDKs, and CLI use. See the [API Reference](https://docs.nexus.xyz/api-reference). --- # 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.nexus.xyz/exchange-layer-1/overview/contributors-and-partners.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.