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

The difference between Events and Function Calls

At its core, not every function call emits an event. Smart contract developers specify when an event should be created and the information contained within. A function call is a transaction that calls a certain function of the smart contract. But it does not necessarily emit an event.

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.

PreviousFunction Call Monitoring: Use CasesNextValue triggers

Last updated 1 year ago