> For the complete documentation index, see [llms.txt](https://faq.tezos-homebase.io/a/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.tezos-homebase.io/a/how-to-configure-your-dao-in-homebase/review-information.md).

# Review Information

&#x20;If you click on next, you will be taken to the review information page, where you will be able to see everything you have configured so far; and if you see anything that you would like to change, you can just click on the edit button and you will be taken to that part of the creator and you will be able to change your settings.\
\
If everything looks correct. And you can click on the launch button.\
\
Connect your wallet if you haven't already. You will first deploy the metadata carrier contract, which is a contract that contains your DAO's metadata information. Next, you would confirm the origination of the actual DAO contract, after the metadata carrier contract has already been deployed. And finally, after the DAO contract has been deployed, you just need to wait for Homebase's indexer to pick up your DAO's contract.\
\
After your DAO has been properly indexed, you will see a button that says, "go to my DAO". And if you click on it, you will be taken to your DAO's page.

**Known Issue**:&#x20;

A DAO fails to deploy every 2 out of 10 times because of a beacon-wallet bottleneck. On Ghostnet we've switched to a managed flow where we just take your parameters and deploy it for you, but we didn't implement this on Mainnet yet. You can try again using another wallet and/or browser. Alternatively, if you provide us (in the [Homebase Discord](https://discord.gg/XufcBNu277)) with the info in the summary page (last screen before deploying), we can put it onchain for you. The wallet that executes the transaction doesn't factor into the functionality of the contract, so it doesn't really matter that it's not you signing.


---

# 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://faq.tezos-homebase.io/a/how-to-configure-your-dao-in-homebase/review-information.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.
