Emitting events in Blockchain / Solidity - Step-by-Step Execution

Concept Flow - Emitting events

Start Transaction

↓

Call Function

↓

Emit Event

↓

Log Event Data

↓

Transaction Ends

↓

Event Available for Listeners

When a function runs, it can emit an event that logs data. This event is stored in the blockchain logs and can be read by apps.

Execution Sample

Blockchain / Solidity

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

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

This code defines an event and emits it inside a function to log a transfer.

Execution Table

Step	Action	Evaluation	Result
1	Start transaction	N/A	Transaction begins
2	Call send() with to=0xABC, amount=100	Check inputs	Inputs valid
3	Emit Sent event	Create event log with from=caller, to=0xABC, amount=100	Event logged on blockchain
4	End transaction	N/A	Transaction confirmed
5	Event available	Listeners can read event data	Event data accessible

💡 Transaction ends after event is emitted and logged

Variable Tracker

Variable	Start	After emit	Final
msg.sender	caller address	caller address	caller address
to	input address	input address	input address
amount	input uint	input uint	input uint
Event Sent	not emitted	emitted with data	emitted with data

Key Moments - 3 Insights

Why do we use 'emit' before the event name?

The 'emit' keyword tells the blockchain to create a log entry for the event. Without 'emit', the event won't be recorded. See execution_table step 3.

Does emitting an event change contract state?

No, emitting an event only logs data. It does not modify variables or contract storage. This is shown in variable_tracker where variables stay the same.

Can external apps read emitted events?

Yes, events are stored in transaction logs and external apps can listen and react to them. See execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what happens at step 3?

A The event is emitted and logged on the blockchain

B The transaction ends without logging

C The function inputs are checked

D The event is removed

💡 Hint

Check execution_table row with Step 3 describing event emission

According to variable_tracker, what is the state of 'amount' after emitting the event?

A Changed to zero

B Remains the input value

C Undefined

D Incremented by one

💡 Hint

Look at 'amount' row in variable_tracker after emit column

If the 'emit' keyword is removed, what changes in the execution flow?

A Event logs twice

B Transaction will fail immediately

C Event will not be logged, so no event data is available

D Function inputs become invalid

💡 Hint

Refer to key_moments about the role of 'emit' and execution_table step 3

Concept Snapshot

Syntax: event EventName(params);
Use 'emit EventName(args);' inside functions.
Emitting events logs data on blockchain.
Events do not change contract state.
External apps listen to events for updates.

Full Transcript

Emitting events in blockchain means creating a log entry during a transaction. When a function runs, it can emit an event using the 'emit' keyword followed by the event name and data. This event is stored in the blockchain logs and can be read by external apps or listeners. Emitting events does not change the contract's variables or state; it only records information. The transaction continues and ends after the event is logged. This helps apps track what happened during transactions without changing the blockchain state.

Practice

1. What is the main purpose of emitting events in a blockchain smart contract?

easy

A. To send signals about important actions to external listeners

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

C. To execute complex calculations inside the contract

D. To create new tokens automatically

Solution

1. Step 1: Understand event purpose

   Events are used to notify external systems about contract actions without heavy storage.

2. Step 2: Compare options

   Only To send signals about important actions to external listeners describes sending signals to outside listeners, which matches event use.

3. Final Answer:

   To send signals about important actions to external listeners -> Option A

4. Quick Check:

   Events notify external listeners = D [OK]

Hint: Events notify outside world, not store big data [OK]

Common Mistakes:

• Thinking events store large data permanently
• Confusing events with token creation
• Believing events run complex calculations

2. Which of the following is the correct syntax to emit an event named Transfer with parameters from, to, and amount in Solidity?

easy

A. event Transfer(from, to, amount);

B. Transfer.emit(from, to, amount);

C. emit Transfer(from, to, amount);

D. emit.Transfer(from, to, amount);

Solution

1. Step 1: Recall Solidity event emission syntax

   In Solidity, events are emitted using the keyword emit followed by the event name and parameters in parentheses.

2. Step 2: Check each option

   emit Transfer(from, to, amount); matches the correct syntax: emit Transfer(from, to, amount);. Others misuse dot notation or keywords.

3. Final Answer:

   emit Transfer(from, to, amount); -> Option C

4. Quick Check:

   emit keyword + event name + params = C [OK]

Hint: Use 'emit EventName(params);' exactly [OK]

Common Mistakes:

• Using dot notation like emit.Transfer()
• Writing event declaration instead of emission
• Placing emit after event name

3. Given the Solidity code snippet:

event Deposit(address indexed sender, uint amount);

function deposit() public payable {
    emit Deposit(msg.sender, msg.value);
}

What happens when the deposit function is called with 1 ether?

medium

A. The function throws an error due to missing return

B. The contract balance decreases by 1 ether

C. No event is emitted because emit keyword is missing

D. An event Deposit is emitted with sender's address and amount 1 ether

Solution

1. Step 1: Analyze the deposit function

   The function emits the Deposit event with the caller's address and the amount sent (msg.value).

2. Step 2: Understand event emission effect

   Calling deposit with 1 ether triggers the event with sender and 1 ether amount; contract balance increases, no error.

3. Final Answer:

   An event Deposit is emitted with sender's address and amount 1 ether -> Option D

4. Quick Check:

   emit Deposit with sender and value = A [OK]

Hint: emit sends event with current call data [OK]

Common Mistakes:

• Thinking contract balance decreases on deposit
• Missing that emit keyword is present
• Expecting return value in void function

4. Identify the error in this Solidity code snippet:

event Approval(address owner, address spender, uint amount);

function approve(address spender, uint amount) public {
    Approval(msg.sender, spender, amount);
}

medium

A. Missing the emit keyword before the event call

B. Event parameters are in wrong order

C. Function must be declared as view

D. Event name should be lowercase

Solution

1. Step 1: Check event emission syntax

   In Solidity, events must be emitted using the emit keyword before calling the event.

2. Step 2: Identify the error in code

   The code calls Approval(...) without emit, causing a syntax error.

3. Final Answer:

   Missing the emit keyword before the event call -> Option A

4. Quick Check:

   emit keyword required before event call = A [OK]

Hint: Always prefix event calls with 'emit' [OK]

Common Mistakes:

• Omitting emit keyword
• Assuming event names are case-insensitive
• Thinking function needs view modifier

5. You want to track token transfers in your smart contract and filter them by sender address efficiently. Which event declaration and emission pattern is best to achieve this?

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

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

hard

A. Do not use indexed to save gas, filter by reading all events externally

B. Use indexed keyword on sender and receiver to enable filtering in event logs

C. Emit event without parameters to reduce complexity

D. Store all transfers in contract storage instead of events

Solution

1. Step 1: Understand indexed keyword usage

   Indexed parameters in events allow efficient filtering by those fields in external tools.

2. Step 2: Evaluate options for tracking transfers

   Use indexed keyword on sender and receiver to enable filtering in event logs uses indexed on sender and receiver, enabling fast filtering by sender address.

3. Final Answer:

   Use indexed keyword on sender and receiver to enable filtering in event logs -> Option B

4. Quick Check:

   indexed parameters enable filtering = B [OK]

Hint: Use indexed for filterable event parameters [OK]

Common Mistakes:

• Avoiding indexed to save gas but losing filtering ability
• Emitting events without parameters
• Storing all data on-chain instead of events