> For the complete documentation index, see [llms.txt](https://s-and-s.gitbook.io/stabilize/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://s-and-s.gitbook.io/stabilize/main-body/team.md).

# Team

<img src="/files/-M_2o7EpukuUHna9n1T0" alt="" data-size="original">&#x20;

The core dev team will stay anon, simly because it seems necessary to us to protect the protocol from higher forces. We are aware that we are part of a completely unregulated, everything-goes financial system (defi), and we assume that some governments will try to regulate it in the not so distant future. One of the few real means these governments might have to take control over protocols in decentralized networks, is to personally attack the heads behind. Therefore, from our point of view, having an anon core team is almost a must to be as future proof and resistant as possibe. We further have the plan to transition the Stabilize protocol into a DAO, without leaders, to make it even more resistant against any higher forces.&#x20;

The core team will do everything it can to make the protocol safe and relyable, by having a clean code and timelocks, supplying audits by respected auditors, and by beeing transparent about our actions.


---

# 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:

```
GET https://s-and-s.gitbook.io/stabilize/main-body/team.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
