> For the complete documentation index, see [llms.txt](https://learn.ember.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.ember.so/ember-protocol/security.md). # Security ## Ember Security and Infrastructure At Ember Protocol, every layer, from vault architecture to strategy management, is designed with continuous assurance in mind. Ember Protocol was co-incubated by teams that have built battle-tested infrastructure that manages over $700M in assets and have had zero security incidents in over 4 years of operating. Security at Ember begins with code and extends into process. Assurance is continuous, not point in time. * Two independent full audits completed by OtterSec and Asymptotic (here’s the [audit](https://ember.so/documents/ember_protocol_audit.pdf)) * Formal verification in progress to mathematically prove key invariants (available mid-November) * Continuous retainer partnerships with OtterSec and Asymptotic, meaning no new code ships without their review of pull requests. * Active bug bounty partnership with HackenProof ([Bug Bounty](https://hackenproof.com/programs/ember-vaults-smart-contracts)) * Secure development lifecycle with mandatory peer review, automated invariant testing, and CI/CD integration. This model replaces point-in-time audits with an active assurance loop. The same engineers and security teams stay engaged across the entire development lifecycle, ensuring every release inherits the context of the last. We extend that philosophy beyond code through layered defence and containment. Risk is modelled across smart contract, market, integration, operational, and user domains, each with built-in circuit breakers that enforce limits, delay withdrawals, validate oracles, and trigger alerts. This creates mechanical containment: when anomalies occur, the system remains controlled, visible, and recoverable. Real-time monitoring through Guardrail ensures that every invariant and circuit breaker is continuously observed and acted upon, transforming potential threats into manageable events. Finally, Ember curates what it connects to. Only audited, battle-tested protocols and proven institutional curators like MEV Capital and Gamma are approved. Transparency completes the loop: public audits, formal verification reports, live monitoring dashboards, verified builds, and an open bug bounty. Security at Ember is not promised; it’s proven, visible, and continuously verified. --- # 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://learn.ember.so/ember-protocol/security.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.