Aegis
  • Introduction
    • Who is Aegis for?
    • How to start using Aegis?
    • How does Aegis work?
      • Supported networks
      • Findings
      • Categorizing your monitored address
      • Backtesting
        • Performing a backtest
      • Smart contract analysis
      • Allowances
  • Add a monitored address
    • Bulk import addresses
  • Add a notification channel
    • Add an email notification channel
    • Add a Slack notification channel
      • Anatomy of your Slack notification
    • Add a Telegram notification channel
      • Anatomy of your Telegram notification
    • Add an SMS notification channel
    • Add a Discord notification channel
      • Anatomy of your Discord notification
    • Webhooks
  • Triggers
    • Trigger Types compatibility matrix
    • Potential Risks
      • Risk Types
      • Risk Levels
      • Retention of Aegis Findings
    • Events
      • Event Listening: Use cases
    • Function Calls
      • Function Call Monitoring: Use Cases
    • The difference between Events and Function Calls
    • Value triggers
      • Transfer Threshold Monitoring: Use Cases
      • Total-Value-Locked (TVL) Monitoring: Use Cases
      • Token Mint Monitoring: Use Cases
    • Wallet Activity
  • Add an alert
    • Alert management
    • Notification limits solutions
  • Panic Button
    • Add a Panic Button
    • How does the Panic Button work?
  • Interact with your smart contract
  • Teams
  • API
  • Aegis dApp
    • Token risk analysis
  • Firewall
  • Pricing
    • LSS Boost
    • Aegis Limitless
    • Aegis Pulse
  • Glossary
  • Release notes
Powered by GitBook
On this page
  1. Triggers

Function Calls

Triggers based on function calls aim to warn users about specific interactions with the observed smart contracts. Aegis tracks every function call associated with the monitored smart contracts, providing real-time insight about unwarranted and potentially malicious interactions.

PreviousEvent Listening: Use casesNextFunction Call Monitoring: Use Cases

Last updated 1 year ago