> For the complete documentation index, see [llms.txt](https://sending-network.gitbook.io/sending.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sending-network.gitbook.io/sending.network/network-instructional-articles/basics/the-team.md). # The Team The team behind SendingNetwork has an impressive entrepreneurial history. In 2010, they launched Dolphin, a popular browser that reached over 200 million users at its peak and was the only browser to make PCWorld's 2011 Top 100 Best Tech Products list. Dolphin was eventually acquired for $90 million. Their second venture focused on AI and secured $100 million in funding. Their motivation for creating SendingNetwork, a decentralized communication infrastructure, stems from an unexpected incident where Google Play removed Dolphin. Despite quick reinstatement due to strong community support, this experience highlighted the drawbacks of centralization and the power of the community. This inspired the idea of developing a Web3 decentralized product to counter such control. --- # 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://sending-network.gitbook.io/sending.network/network-instructional-articles/basics/the-team.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.