> For the complete documentation index, see [llms.txt](https://docs.rocksolid.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rocksolid.network/integration/onboarding-guide.md). # Onboarding Guide ## General Timeline * Week 1: * Vault design and mandate agreed * Smart contracts deployed * RockSolid front-end and app live * Week 2: * Partner integration underway or complete * Weeks 3-4: * Predeposits received from partners, LPs, and/or whales and deployed into DeFi * Public launch, marketing and GTM campaign finalized ## Key Steps Required for Launch ### 1. Decide integration locations (any combo of the below): * RockSolid website and app * Your website and app * Custom integration (e.g. into a wallet or exchange) The deployment of the smart contracts and integration to the RockSolid website and app can occur within a day. Integration with your website/app or a custom integration may take longer. RockSolid devs can handle as much or as little of the integration work you prefer. ### 2. Vault design Decisions must be made upon each of these dimensions with your team before deploying. RockSolid is able to suggest default values for each of these decisions: * Token symbol and name * Vault name and description * Vault logo * Do you want the vault to be public or private? * Deposit asset (e.g. ETH, USDC, etc.) and on what network? * Fee structure (management and performance fee) * Strategy mandate (strategies, APR target, leverage, diversification requirements, etc) ### 3. Go-to-Market * Secure pre-deposits from LPs / whales * Prepare launch comms and marketing assets * Secure podcasts / interviews / etc to coincide with launch --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.rocksolid.network/integration/onboarding-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.