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
  2. Function Calls

Function Call Monitoring: Use Cases

PreviousFunction CallsNextThe difference between Events and Function Calls

Last updated 1 year ago

Function call monitoring is particularly useful in cases when event listening falls short of expectations. This is particularly true for instances when some smart contract function calls have not been coded to emit an event. Users may thus find that event listening alone would leave huge gaps in monitoring crucial on-chain activity.

Function call monitoring is also useful when pre-configured event information is too vague. For example, ERC20 contracts typically include both the and functions, yet just one event. Looking at the event alone, it may be difficult to determine which function was called. This ambiguity can be resolved through precise function call monitoring, where each call is distinctly tracked.

Project teams may wish to set up function call alerts for their own contracts, particularly for functions that have not been coded to emit an associated event. Aegis can be configured to send out an immediate SMS notification that warns of unplanned function calls that may signal the initial stages of an imminent exploit.

Individual investors may wish to monitor function calls that relate to token price movements. Aegis alerts can help traders immediately focus attention on specific token burns, mints, and other governance structure changes that may not emit smart contract events.

We recommend discussing with your smart contract developers or liaising with the Lossless team to determine which events and function calls merit monitoring. Some high-risk events are already automatically tracked as Potential Risks. Meanwhile, project teams may wish to monitor certain events and function calls for reasons beyond security, such as for testing or analytics.

Transfer
TransferFrom
Transfer