IMAA documentation

IMAA is a smart contract monitoring and alerting platform for EVM chains and Solana. Point it at any deployed contract or program, 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 six primitives. Each one is independent and composable:

  1. Contract — an on-chain address you want to watch, on one of the supported chains. On EVM chains its ABI is auto-fetched on add; on Solana you point IMAA at a program and supply (or auto-resolve) its IDL.
  2. Monitor target — a measurable signal on that contract: event frequency, transaction rate, revert rate, latency, value transferred, oracle price/staleness, or a statistical anomaly.
  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, HTTP webhook, Discord, or PagerDuty.
  5. Bridge configuration — for contracts that implement a LayerZero V2 OApp interface, IMAA automatically reads the DVN set for each route and surfaces a risk score. No setup required. DVN Detection →
  6. Monitored agent — an AI agent acting as an oracle (prediction resolver, LLM oracle, on-chain advisor). IMAA probes the agent, builds behavioural baselines, and alerts on drift or compromise. AI Agent Monitoring →

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