> ## Documentation Index
> Fetch the complete documentation index at: https://docs.solhedge.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Common questions about SolHedge.

<AccordionGroup>
  <Accordion title="Is SolHedge custodial?">
    No. SolHedge is fully non-custodial. Funds move directly between the liquidity pool and your wallet. The protocol never takes custody of your assets.
  </Accordion>

  <Accordion title="Do I need to understand perpetuals or hedging to use SolHedge?">
    No. The AI handles all hedge logic automatically. You deposit, activate, and the protocol manages range, hedging, rebalancing, and compounding for you.
  </Accordion>

  <Accordion title="What is Auto-Hedge and how do I unlock it?">
    Auto-Hedge automatically opens offsetting positions to reduce impermanent loss and directional exposure. It's a Premium feature, unlocked with a one-time payment of 200,000 \$SHEDGE. See [Token Utility](/token/utility).
  </Accordion>

  <Accordion title="Has SolHedge been audited?">
    Yes. Smart contracts have been penetration tested by Daemon. Audit reports are available to institutional counterparties upon request.
  </Accordion>

  <Accordion title="What happens to my position when the AI detects high risk?">
    Liquidity may be pulled back to stablecoins to protect capital. This stops fee accrual and realizes the position at that point, so it's used only when multiple risk signals confirm together. See the [Risk Framework](/security/risk-framework).
  </Accordion>

  <Accordion title="How does $SHEDGE generate real demand?">
    Demand comes from Premium Access payments and Market Making service fees, both paid in \$SHEDGE, plus an automatic buyback-and-burn funded by MM revenue. See [Tokenomics](/token/tokenomics).
  </Accordion>

  <Accordion title="Was there a presale or team allocation?">
    No. \$SHEDGE launched as a fair launch with a fixed supply of 1 billion tokens, with no pre-mine, no team allocation, and no VC allocation.
  </Accordion>
</AccordionGroup>