> 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/overview/contributors-and-partners.md). # Contributors & Partners ## Team The Nexus team brings together deep expertise in financial markets, AI, and large-scale systems engineering — with academic backgrounds from Stanford, UC Berkeley, UCLA, University College London, and Brown, and operational experience across leading technology and finance organizations including Google, Amazon, Microsoft, PwC, and Mozilla. ## Advisors Nexus is advised by distinguished cryptographers and leaders from institutions including NYU, MIT, Harvard, UC Berkeley, and Cornell, and from the Ethereum Foundation, Zcash, Chainlink, and Bitso. ## Investors Nexus is backed by leading crypto investors — led by **Dragonfly**, **Lightspeed**, and **Pantera** — alongside Faction, SV Angel, Alliance, Blockchain Builders Fund, and the Stanford Blockchain Accelerator. ## Technology & protocol partners * **M0** — collaborating on [USDX](/network/building-on-nexus/tokens-and-bridges.md), the native dollar stablecoin (in development). * **Hyperlane** — cross-chain [bridging](/network/building-on-nexus/tokens-and-bridges/bridging.md) for NEX between Ethereum and BSC. Nexus works with a growing ecosystem of partners across AI, zkVM, and crypto. See [nexus.xyz/ecosystem](https://nexus.xyz/ecosystem) for the current list. ## Build on Nexus Nexus is permissionless and EVM-compatible, so any team can build on it — and, over time, launch their own markets on the exchange. See [Build on Nexus](/network/building-on-nexus.md). --- # 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://docs.nexus.xyz/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 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.