# Securing Napier

Security has been a top priority at every stage of building **Napier v2**.

To date, Napier has invested **over $1 million** into ensuring the security of the protocol.

The vision for transforming Napier into a **modular protocol** began in early 2024. Since then, multiple code designs were explored as proofs of concept — even before the official launch of Napier v1. Unlike the conventional approach where a protocol is built first and only later reviewed by auditors, Napier v2’s development integrated security considerations from the ground up, across every layer.

* [**Technical partners**](/security/securing-napier/technical-partners.md)**:** Industry-leading security team and individuals contributed as hands-on partners to stress-test and refine the codebase.
* [**Bug bounty**](/security/securing-napier/bug-bounty.md)**:** Coming soon — a public program to incentivize responsible disclosure.
* [**Risk documentation**](/security/securing-napier/risk-documentation.md)**:** Clear, accessible explanations of potential risks when using the Napier Protocol and its interfaces.


---

# 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.napier.finance/security/securing-napier.md?ask=<question>
```

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.
