Why events communicate contract activity in Blockchain / Solidity - See It in Action

Why Events Communicate Contract Activity

📖 Scenario: Imagine you have a smart contract on the blockchain that tracks simple transactions. You want to know when someone sends money or performs an action without constantly checking the contract's state. Events help by sending messages that something happened.

🎯 Goal: You will create a simple Solidity contract that uses an event to announce when a user sends money. This shows how events communicate contract activity clearly and efficiently.

📋 What You'll Learn

Create a Solidity contract named SimpleBank

Declare an event named DepositMade with parameters address account and uint amount

Create a deposit function that accepts Ether and emits the DepositMade event

Add a public mapping balances to track user balances

Emit the event inside the deposit function after updating the balance

💡 Why This Matters

🌍 Real World

Events are used in blockchain apps to notify wallets, user interfaces, and other contracts about changes without expensive data reads.

💼 Career

Understanding events is essential for blockchain developers to build interactive and efficient decentralized applications.

1

Create the contract and balances mapping

Write a Solidity contract named SimpleBank and inside it declare a public mapping called balances that maps address to uint.

Blockchain / Solidity

contract SimpleBank {
    // Your code here
}

Hint

Start by writing contract SimpleBank { } and inside it add mapping(address => uint) public balances;

2

Declare the DepositMade event

Inside the SimpleBank contract, declare an event named DepositMade that has two parameters: address account and uint amount.

Blockchain / Solidity

pragma solidity ^0.8.0;

contract SimpleBank {
    mapping(address => uint) public balances;
    // Your code here
}

Hint

Use the keyword event followed by the event name and parameters inside parentheses.

3

Create the deposit function and emit the event

Add a public payable function named deposit inside SimpleBank. Inside it, increase the sender's balance in balances by msg.value and then emit the DepositMade event with msg.sender and msg.value.

Blockchain / Solidity

pragma solidity ^0.8.0;

contract SimpleBank {
    mapping(address => uint) public balances;
    event DepositMade(address account, uint amount);

    // Your code here
}

Hint

Remember to mark the function as payable to accept Ether. Use emit to send the event.

4

Test the contract by calling deposit and observe event

Write a comment line that explains that when deposit is called, the DepositMade event will notify listeners about the deposit.

Blockchain / Solidity

pragma solidity ^0.8.0;

contract SimpleBank {
    mapping(address => uint) public balances;
    event DepositMade(address account, uint amount);

    function deposit() public payable {
        balances[msg.sender] += msg.value;
        emit DepositMade(msg.sender, msg.value);
    }
}

// Your explanation here

Hint

Write a comment starting with // explaining the event's purpose.

Practice

1. Why do smart contracts use events to communicate activity?

easy

A. To send messages about contract actions to external listeners

B. To store large amounts of data permanently on the blockchain

C. To increase the gas cost of contract execution

D. To prevent users from interacting with the contract

Solution

1. Step 1: Understand the purpose of events in smart contracts

   Events are designed to notify external systems about what happens inside the contract without storing data permanently on-chain.

2. Step 2: Identify the correct use of events

   Events send messages to external listeners, like user interfaces or monitoring tools, about contract actions.

3. Final Answer:

   To send messages about contract actions to external listeners -> Option A

4. Quick Check:

   Events notify external systems = C [OK]

Hint: Events notify outside world about contract actions [OK]

Common Mistakes:

• Thinking events store large data permanently
• Believing events increase gas cost unnecessarily
• Confusing events with access control mechanisms

2. Which of the following is the correct syntax to declare an event in Solidity?

easy

A. event Transfer function(address from, address to, uint amount);

B. event Transfer(address indexed from, address indexed to, uint amount);

C. event Transfer {address from, address to, uint amount};

D. event Transfer = (address from, address to, uint amount);

Solution

1. Step 1: Recall Solidity event declaration syntax

   Events are declared with the keyword 'event', followed by the event name and parameters in parentheses, ending with a semicolon.

2. Step 2: Identify the correct syntax among options

   event Transfer(address indexed from, address indexed to, uint amount); matches the correct Solidity syntax with 'indexed' keywords for filtering.

3. Final Answer:

   event Transfer(address indexed from, address indexed to, uint amount); -> Option B

4. Quick Check:

   Correct event syntax uses parentheses and semicolon = D [OK]

Hint: Events use 'event Name(params);' syntax in Solidity [OK]

Common Mistakes:

• Using '=' instead of parentheses
• Using curly braces instead of parentheses
• Adding 'function' keyword in event declaration

3. Given the Solidity event and function below, what will be emitted when transfer(0x123, 100) is called?

event Transfer(address indexed from, address indexed to, uint amount);

function transfer(address to, uint amount) public {
    emit Transfer(msg.sender, to, amount);
}

medium

A. No event emitted because emit keyword is missing

B. Transfer event with from = 0x123, to = caller address, amount = 100

C. Transfer event with from = caller address, to = 0x123, amount = 100

D. Transfer event with from = 0x0, to = 0x123, amount = 0

Solution

1. Step 1: Understand the function call and event emission

   The function emits a Transfer event with 'msg.sender' as 'from', 'to' as the passed address, and 'amount' as passed.

2. Step 2: Apply the call parameters

   Calling transfer(0x123, 100) sets 'to' to 0x123 and 'amount' to 100; 'msg.sender' is the caller's address.

3. Final Answer:

   Transfer event with from = caller address, to = 0x123, amount = 100 -> Option C

4. Quick Check:

   emit Transfer(msg.sender, to, amount) = A [OK]

Hint: emit uses caller as from, passed args as to and amount [OK]

Common Mistakes:

• Confusing 'from' and 'to' parameters
• Forgetting 'emit' keyword
• Assuming default zero addresses

4. Identify the error in the following Solidity code snippet that prevents the event from being emitted:

event Deposit(address indexed sender, uint amount);

function deposit(uint amount) public {
    Deposit(msg.sender, amount);
}

medium

A. Event parameters are in wrong order

B. Function must be marked as 'payable' to emit events

C. Event name should be lowercase

D. Missing 'emit' keyword before the event call

Solution

1. Step 1: Review event emission syntax in Solidity

   Since Solidity 0.4.21, events must be emitted using the 'emit' keyword.

2. Step 2: Check the code for missing 'emit'

   The code calls 'Deposit(msg.sender, amount);' without 'emit', so the event won't be emitted.

3. Final Answer:

   Missing 'emit' keyword before the event call -> Option D

4. Quick Check:

   Events require 'emit' keyword = B [OK]

Hint: Always use 'emit' before event calls in Solidity [OK]

Common Mistakes:

• Omitting 'emit' keyword
• Assuming event names are case-insensitive
• Thinking 'payable' is required for events

5. You want to track token transfers in your contract efficiently. Which approach best uses events to minimize gas costs and allow external monitoring?

hard

A. Emit an event with indexed sender and receiver addresses and the amount transferred

B. Store all transfer details in a public array inside the contract

C. Use a mapping to save transfer history and emit no events

D. Emit events without indexed parameters to save gas

Solution

1. Step 1: Understand gas cost and event indexing

   Indexed event parameters allow efficient filtering by external tools and cost less gas than storing data on-chain.

2. Step 2: Evaluate options for tracking transfers

   Emitting events with indexed sender and receiver is efficient and allows external monitoring without high storage costs.

3. Final Answer:

   Emit an event with indexed sender and receiver addresses and the amount transferred -> Option A

4. Quick Check:

   Indexed events minimize gas and enable monitoring = A [OK]

Hint: Use indexed event params for efficient tracking [OK]

Common Mistakes:

• Storing all data on-chain increases gas costs
• Not indexing event parameters reduces filtering ability
• Avoiding events leads to poor external monitoring