> For the complete documentation index, see [llms.txt](https://docs.lossless.io/aegis/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lossless.io/aegis/triggers.md).

# Triggers

Aegis smart contract monitoring system is based on triggers. Triggers are observable on-chain events that set off alerts through user notification channels. Within Aegis, triggers fall into four broad categories based on the type of detectable on-chain activity:<br>

**Potential Risks** triggers are derived from Findings and related to smart contract security issues spotted by Aegis. These are composed of both specific smart contract Risk Type(s) and an AI-generated Risk Score based on suspicious activity.

**Events** triggers are related to a change of state in the deployed smart contract. These are highly customizable and inform developers, platforms, and web3 stakeholders that a potentially significant event has occurred.

**Function Calls** triggers are related to interactions with the monitored smart contracts. Aegis detects and notifies users when any smart contract function is called on-chain.

**Value** triggers are related to a broad array of value-based events:

&#x20;   **Transfer Thresholds** trace asset movements to and from a monitored address.&#x20;

&#x20;   **TVL Changes** monitor fluctuations in Total Value Locked.

&#x20;  **Token Mints** track whether an ERC-type contract is minting new tokens.

**Wallet Activity** triggers are reserved for all wallet actions on the chain like Transfer, Swap or Approve. Currently, this feature can only be toggled “on” or “off” and it is not possible to pick and choose which specific activity to track. Wallet Activity functionality is exclusive to wallet-type monitored addresses.


---

# 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://docs.lossless.io/aegis/triggers.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.