> For the complete documentation index, see [llms.txt](https://docs.sherpa.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sherpa.trade/sherpaearn-vault/quick-start-guide/f.a.q..md). # F.A.Q. ## Depositing & Withdrawing **Q: What is the minimum deposit?** \ A: 1 `USDC` **Q: What is the maximum deposit?** \ A: Whatever the spare capacity is on the vault for a given network. We dont set per user caps, so the max is entirely dependent upon what space the vaults have available. **Q: When can I withdraw?**\ A: Anytime. Standard withdrawals take 1 cycle ( less than 24 hours). **Q: Why do I have to wait a cycle?**\ A: This allows the vault to settle positions and ensures fair pricing for all users. **Q: I just deposited, why did'nt I get shares (`shUSD`) immediately?**\ A: Shares are minted when the current cycle ends and the new cycle begins (approximately every 24 hours). ## General **Q: Which chain should I use?**\ A: For smaller deposits, Base or Monad are recommended for lower fees. For large depositors Ethereum provides larger capacity. **Q: Can I deposit on one chain and withdraw on another**\ A: Yes! Bridge your `shUSD` to any integrated chain, then withdraw to `USDC` on that chain. **Q: Does bridging cost anything?**\ A: A Small network fee and CCIP messaging fee applies. Aside from that no, your `shUSD` will be transferred across chains at a 1:1 ratio. **Q: Are prices the same across all chains?**\ A: Yes. All chains maintain the same global price per `shUSD`, synchronized each and every cycle. **Q: Are there any fees?**\ A: Management fees and performance fees apply. **Q: What happens if the website goes down?**\ A: You can still interact directly with smart contracts via Etherscan. Your funds always remain safe on-chain. Q: What is `sherpaUSD`?\ A: An non user-facing accounting token that tracks the `USDC` deposited into the vault at a 1:1 ratio. ## Yield & Points **Q: How often are yields distributed?**\ A: Yields are automatically compounded each cycle (approximately every 24 hours). No manual claiming needed. **Q: How often are points distributed?**\ A: Routine points distributions are made each cycle (approximately every 24 hours). Bonus points are issues once individualmilestones are met. **Q: When can I redeem Sherpa points?**\ A: At token launch (date TBA). Points are tracked in the dashboard until then. **Q: What's the redemption ratio for points?**\ A: 10 Sherpa points = 1 Sherpa token (10:1 ratio) **Q: Can I choose to opt out of earning points from the Launchpool?**\ A: Yes, just dont claim your `shUSD` from the vault. You'll receive 100% of your yield in `USDC`. No points earned. **Q: Can the team access my funds?**\ A: No. The vault is non-custodial. Only you control your `shUSD` tokens. **Q: Do i get different amounts of yield by depositing on different chains?**\ A: No, all chains share the exact same yield growth rate. ## Risks **Q: Is Launchpool risky?**\ A: No additional risk to your principal. You're only allocating yield, not your deposit. **Q: Can I lose money?**\ A: Yes. While strategies aim for consistent returns, losses are possible. Only deposit funds you can afford to lose. --- # 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.sherpa.trade/sherpaearn-vault/quick-start-guide/f.a.q..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.