IMAA documentation

IMAA is a smart contract monitoring and alerting platform for EVM chains. Point it at any deployed contract, define the on-chain signals that matter to you, and get notified the moment something breaches a threshold — by email, Slack, SMS, or signed webhook.

It is built for protocol teams, security engineers, and operators who need confidence that their production contracts are behaving the way they expect, without writing and hosting bespoke indexing code.

How the pieces fit together

IMAA is built around four primitives. Each one is independent and composable:

1. Contract — an on-chain address you want to watch, on one of the supported chains. Its ABI is auto-fetched on add.
2. Monitor target — a measurable signal on that contract: event frequency, transaction rate, revert rate, latency, or specific function calls.
3. Alert rule — a threshold, comparison operator, time window, and severity applied to a monitor target. When the rule trips, an alert event is recorded.
4. Channel — where the alert goes: email, Slack webhook, SMS, or HMAC-signed HTTP webhook.

A typical setup is one contract with two or three monitor targets, each tied to one or more alert rules, each routed to the right channel for the right team.

Where to next

• Quick start — get your first alert firing in five minutes.
• Alert rules — operators, windows, and idempotency semantics.
• Public API — programmatic access for Pro and above.