Event filtering in Blockchain / Solidity - Step-by-Step Execution

Concept Flow - Event filtering

Start: Listen to blockchain events

↓

Receive event data

↓

Check event type or attributes

↓

Process event

↓

Update state or UI

↓

Repeat

The program listens to blockchain events, checks if each event matches filter criteria, processes matching events, and ignores others.

Execution Sample

Blockchain / Solidity

filter = {"event": "Transfer"}
for event in blockchain_events:
    if event["type"] == filter["event"]:
        print(f"Transfer from {event['from']} to {event['to']}")

This code filters blockchain events to only show 'Transfer' events and prints their details.

Execution Table

Step	Event Data	Condition (event type == 'Transfer')	Action	Output
1	{"type": "Approval", "owner": "A", "spender": "B"}	False	Ignore event
2	{"type": "Transfer", "from": "A", "to": "B", "value": 100}	True	Process event	Transfer from A to B
3	{"type": "Mint", "to": "C", "value": 50}	False	Ignore event
4	{"type": "Transfer", "from": "B", "to": "C", "value": 25}	True	Process event	Transfer from B to C
5	No more events	N/A	Stop loop

💡 No more events to process, loop ends.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
event	None	{"type": "Approval", "owner": "A", "spender": "B"}	{"type": "Transfer", "from": "A", "to": "B", "value": 100}	{"type": "Mint", "to": "C", "value": 50}	{"type": "Transfer", "from": "B", "to": "C", "value": 25}	No more events

Key Moments - 2 Insights

Why do some events get ignored even though they come from the blockchain?

Events are ignored if their type does not match the filter condition (see execution_table rows 1 and 3 where event type is not 'Transfer'). Only matching events are processed.

What happens when there are no more events to process?

The loop stops because there are no more events (see execution_table row 5). This prevents infinite waiting.

Visual Quiz - 3 Questions

Look at the execution table, what is the event type at step 2?

A "Approval"

B "Transfer"

C "Mint"

D "Burn"

💡 Hint

Check the 'Event Data' column at step 2 in the execution_table.

At which step does the condition become false for the first time?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Condition' column in the execution_table for the first 'False' value.

If the filter changed to event type 'Mint', which step would process an event?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Check which event has type 'Mint' in the 'Event Data' column.

Concept Snapshot

Event filtering listens to blockchain events.
It checks each event's type or attributes.
Only matching events are processed.
Others are ignored.
This helps focus on relevant data.

Full Transcript

This visual execution shows how event filtering works in blockchain programming. The program listens to events, checks if each event matches the filter criteria (like event type 'Transfer'), and processes only those events. Non-matching events are ignored. The execution table traces each event, the condition check, and the action taken. Variables track the current event being processed. Key moments clarify why some events are ignored and when the loop stops. The quiz tests understanding of event types and filtering steps.

Practice

1.

What is the main purpose of event filtering in blockchain applications?

easy

A. To encrypt blockchain data

B. To create new blockchain events

C. To mine new blocks faster

D. To listen only to specific events that match certain criteria

Solution

1. Step 1: Understand event filtering concept

   Event filtering allows you to listen only to events that match specific parameters or conditions.

2. Step 2: Identify the main purpose

   This helps reduce unnecessary data processing and improves app performance by focusing on relevant events.

3. Final Answer:

   To listen only to specific events that match certain criteria -> Option D

4. Quick Check:

   Event filtering = selective listening [OK]

Hint: Event filtering means listening only to events you want [OK]

Common Mistakes:

• Confusing event filtering with event creation
• Thinking event filtering speeds up mining
• Believing event filtering encrypts data

2.

Which of the following is the correct syntax to filter events by a parameter named user in a blockchain event listener?

contract.events.Transfer({ filter: { ??? } })

easy

A. { user: '0x123...' }

B. { 'user' }

C. [ user ]

D. user = '0x123...'

Solution

1. Step 1: Understand filter syntax

   Filters use an object with key-value pairs where keys are parameter names and values are filter values.

2. Step 2: Match correct syntax

   The correct syntax is an object with the parameter name as key and the desired value, like { user: '0x123...' }.

3. Final Answer:

   { user: '0x123...' } -> Option A

4. Quick Check:

   Filter = object with key-value pairs [OK]

Hint: Filters use {paramName: value} object syntax [OK]

Common Mistakes:

• Using array or string instead of object for filters
• Writing filter as assignment instead of object
• Omitting quotes around string values

3.

Given the following code snippet, what events will be received?

contract.events.Transfer({ filter: { from: '0xabc...' }, fromBlock: 100, toBlock: 200 })

Assuming events with from address '0xabc...' occurred at blocks 90, 150, and 210.

medium

A. Only event at block 150

B. Events at blocks 90, 150, and 210

C. Events at blocks 90 and 150

D. No events

Solution

1. Step 1: Analyze filter parameters

   The filter listens for events where 'from' equals '0xabc...'. The block range is from 100 to 200.

2. Step 2: Check event blocks against filter

   Events at blocks 90 and 210 are outside the block range, so only the event at block 150 matches both filter and block range.

3. Final Answer:

   Only event at block 150 -> Option A

4. Quick Check:

   Filter + block range = event at block 150 only [OK]

Hint: Events must match filter and block range [OK]

Common Mistakes:

• Ignoring block range and including all matching events
• Including events outside the block range
• Confusing filter parameter with block number

4.

Identify the error in this event filter code snippet:

contract.events.Approval({ filter: { owner: 0xabc123 }, fromBlock: 'latest' })

medium

A. Filter object should be an array

B. The filter value 0xabc123 should be a string

C. fromBlock cannot be 'latest'

D. The event name 'Approval' is incorrect

Solution

1. Step 1: Check filter parameter types

   Filter values must be strings for addresses, but 0xabc123 is missing quotes, so it's treated as a variable or number.

2. Step 2: Validate other parts

   The event name and fromBlock usage are valid; fromBlock can be 'latest'. Filter should be an object, not an array.

3. Final Answer:

   The filter value 0xabc123 should be a string -> Option B

4. Quick Check:

   Address filter values must be strings [OK]

Hint: Address filters need quotes around them [OK]

Common Mistakes:

• Omitting quotes around address strings
• Thinking fromBlock 'latest' is invalid
• Using array instead of object for filter

5.

You want to listen to Transfer events where the value is greater than 1000 tokens. Which approach correctly filters these events?

// Assume event signature: Transfer(address from, address to, uint256 value)

hard

A. Use filter: { value: '>1000' }

B. Use filter: { value: val => val > 1000 }

C. Filter events after receiving all by checking value > 1000 in code

D. Set fromBlock and toBlock to limit event range

Solution

1. Step 1: Understand filter limitations

   Event filters only support exact matches or arrays of values, not comparison operators like greater than.

2. Step 2: Choose correct approach

   To filter by value > 1000, you must receive events first and then check the value in your code logic.

3. Final Answer:

   Filter events after receiving all by checking value > 1000 in code -> Option C

4. Quick Check:

   Filters do exact matches; use code for range checks [OK]

Hint: Filters match exact values; use code for greater than checks [OK]

Common Mistakes:

• Trying to use comparison operators in filter
• Assuming string '>1000' works as filter
• Confusing block range with value filtering