> For the complete documentation index, see [llms.txt](https://docs.stability.nexus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stability.nexus/about-us/stable-nest/hatching-requirements.md).

# Hatching Requirements

A project that is **nesting** through the Stable Nest program can be considered **hatched** when all of the following requirements are satisfied:

* [ ] Smart contracts must be thoroughly reviewed by at least 2 knights of The Stable Order.
* [ ] Smart contracts must be deployed on: Ethereum Classic, Ethereum, Polygon, BSC, Base.
* [ ] The project must have a logo.
* [ ] The project must have a favicon.
* [ ] The frontend must have proper title and metadata.
* [ ] The frontend must have proper open graph metadata, to ensure that it is shown well when shared in social media (Discord, Telegram, Twitter, LinkedIn).
* [ ] The frontend must have a footer, containing the Stability Nexus's logo and pointing to the social media accounts of the Stability Nexus.
* [ ] The frontend must be deployed under a https\://\<project>.stability.nexus domain.
* [ ] The project's repos should contain ReadMe files according to [this ReadMe template](https://github.com/StabilityNexus/Template-Repo/blob/main/README.md).&#x20;
* [ ] The project must be listed in <https://stability.nexus/protocols> .


---

# 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.stability.nexus/about-us/stable-nest/hatching-requirements.md?ask=<question>&goal=<endgoal>
```

`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.