# Incident history **No loss of depositor funds since launch in October 2020.** Chamber's core vault contracts (and the dHEDGE contracts they inherit from) have been live continuously on Ethereum mainnet since October 2020, and later on Polygon, Optimism, Arbitrum, Base, Plasma, and HyperEVM. Across that period, no depositor has lost funds to a contract exploit, oracle failure, or integration bug in Chamber. This isn't a claim that nothing has ever gone wrong in DeFi, or that the ecosystem around Chamber (integrated protocols, bridges, wallets, markets) has been incident-free. It is a claim about the Chamber contracts themselves: no successful exploit, no recovery event, no pause-and-socialise moment. ## What this doesn't mean * **It doesn't mean vaults can't lose money.** Managers can make bad trades. Markets move. See [Risk model](/security/risk-model.md) and [Deposit: risks](/deposit/risks.md) for what's actually at stake. * **It doesn't mean future incidents are impossible.** A clean history reduces risk; it doesn't eliminate it. Treat the bug bounty and ongoing audits as the forward-looking defence. * **It doesn't cover third-party protocols.** A vault exposed to an integrated lending market inherits that market's risk. The Guard System restricts what a vault can touch, but it can't prevent a whitelisted protocol from having its own problems. ## How to verify The cleanest way to confirm this is the onchain record. Vault deployments, fee mints, deposits, and withdrawals are all visible from the contract addresses. No emergency pauses, no post-incident redeploys, no retroactive socialisations. If Chamber disclosed an incident in future, it would be documented here with date, scope, and response — in that order. ## See also * [Audits](/security/audits.md) — the reviews that have kept the contracts on the track record above * [Bug bounty](/security/bug-bounty.md) — the live program for anyone finding something the audits missed * [Risk model](/security/risk-model.md) — what the track record does and doesn't imply --- # Agent Instructions: 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: ``` GET https://docs.chamberfi.com/security/incident-history.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.