> For the complete documentation index, see [llms.txt](https://eosi-finance-1.gitbook.io/eosi-finance-documentations/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eosi-finance-1.gitbook.io/eosi-finance-documentations/eosi-finance/10-quality-assurance-and-risk-management/10.2-ai-driven-monitoring-and-bsk-protection.md).

# 🛰️ 10.2 AI‑Driven Monitoring and BSK Protection

To protect users from malicious bots, front‑running and manipulation, <mark style="color:$primary;">EOSI Finance</mark> implements:

* **AI Risk Management:** AI monitors each trade in real time. If a strategy deviates significantly from its expected risk profile or market conditions change abruptly, the AI may block or inform the user to adjust trades. It depends on the user whether to adjust trades or not.
* **Bot Snipper Killer (BSK):** BSK is a proprietary mechanism developed to thwart front‑running bots. It combines public‑private smart contracts to hide transaction details until execution and uses randomised timing to prevent sandwich attacks.
* **Multi‑Layered Security:** data encryption, multi‑sig wallets, hardware security modules (HSMs) and regular security audits protect user funds and ensure smart contracts remain tamper‑proof.
* **Transparent Logs:** every decision by the AI and every executed trade is recorded on‑chain, creating an immutable audit trail.

Users may face smart‑contract bugs, market volatility, liquidity shortages or oracle failures. Participants must perform their own due diligence and must remember that no amount of prevention/protection can FULLY eliminate all risks.


---

# 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://eosi-finance-1.gitbook.io/eosi-finance-documentations/eosi-finance/10-quality-assurance-and-risk-management/10.2-ai-driven-monitoring-and-bsk-protection.md?ask=<question>&goal=<endgoal>
```

`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.