Event-driven architecture patterns in Blockchain / Solidity

Introduction

Event-driven architecture helps blockchain systems react quickly to changes by using events as signals. It makes programs more flexible and easier to manage.

When you want your blockchain app to respond immediately to transactions or state changes.

When building decentralized apps that need to update user interfaces based on blockchain events.

When you want to separate different parts of your blockchain system for better organization.

When you need to track and log important actions happening on the blockchain.

When you want to trigger automatic processes after certain blockchain events occur.

Syntax

Blockchain / Solidity

contract MyContract {
    event MyEvent(address indexed sender, uint value);

    function doSomething(uint _value) public {
        emit MyEvent(msg.sender, _value);
    }
}

event declares an event that can be listened to outside the contract.

emit sends the event with data when something happens.

Examples

This example shows a Transfer event emitted when tokens move from one address to another.

Blockchain / Solidity

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);
}

This example emits an event when a new user registers, sending their address and name.

Blockchain / Solidity

event NewUser(address indexed userAddress, string userName);

function registerUser(string memory _name) public {
    // registration logic
    emit NewUser(msg.sender, _name);
}

Sample Program

This smart contract stores a number and emits an event every time the number changes. The event tells who changed it and the new value.

Blockchain / Solidity

pragma solidity ^0.8.0;

contract SimpleEvent {
    event ValueChanged(address indexed changer, uint newValue);

    uint public value;

    function updateValue(uint _value) public {
        value = _value;
        emit ValueChanged(msg.sender, _value);
    }
}

Important Notes

Events are stored in the blockchain logs and are cheaper than storing data on-chain.

Use indexed to make event parameters searchable.

Listening to events helps front-end apps update without constant polling.

Summary

Events signal important actions in blockchain contracts.

Emit events to notify outside listeners about changes.

Event-driven patterns improve responsiveness and organization.

Practice

1. What is the main purpose of event-driven architecture in blockchain applications?

easy

A. To allow smart contracts to emit events that trigger automatic responses

B. To store large amounts of data on the blockchain

C. To speed up the mining process

D. To encrypt transactions for security

Solution

1. Step 1: Understand event-driven architecture basics

   Event-driven architecture means systems react automatically to events or actions.

2. Step 2: Apply this to blockchain context

   In blockchain, smart contracts emit events that apps listen to and respond automatically.

3. Final Answer:

   To allow smart contracts to emit events that trigger automatic responses -> Option A

4. Quick Check:

   Event-driven architecture = automatic reactions to events [OK]

Hint: Event-driven means automatic reaction to smart contract events [OK]

Common Mistakes:

• Confusing event-driven with data storage
• Thinking it speeds up mining
• Mixing encryption with event handling

2. Which of the following is the correct syntax to listen for an event named Transfer in a blockchain app using JavaScript?

easy

A. contract.listen('Transfer', function(from, to, amount) {});

B. contract.emit('Transfer', (from, to, amount) => {});

C. contract.on('Transfer', (from, to, amount) => { /* handle event */ });

D. contract.catch('Transfer', (from, to, amount) => {});

Solution

1. Step 1: Identify correct event listening method

   In JavaScript blockchain libraries, on is used to listen for events.

2. Step 2: Check syntax for event callback

   The callback receives event parameters like from, to, and amount.

3. Final Answer:

   contract.on('Transfer', (from, to, amount) => { /* handle event */ }); -> Option C

4. Quick Check:

   Use on to listen for events [OK]

Hint: Use .on() method to listen for blockchain events in JS [OK]

Common Mistakes:

• Using .emit() instead of .on() to listen
• Using .listen() which is invalid
• Using .catch() which is for errors

3. Given this Solidity event and JavaScript listener:

event Deposit(address indexed user, uint amount);
contract.on('Deposit', (user, amount) => { console.log(amount.toString()); });

What will be printed if the event is emitted with amount = 500?

medium

A. 0x1f4

B. 500

C. undefined

D. Error: amount.toString is not a function

Solution

1. Step 1: Understand event parameters

   The event emits amount as a number (uint) which is received in JS as a BigNumber or number.

2. Step 2: Check the listener code

   The listener calls amount.toString() which converts the number 500 to string "500".

3. Final Answer:

   500 -> Option B

4. Quick Check:

   amount.toString() converts number 500 to string '500' [OK]

Hint: toString() converts number to string for console output [OK]

Common Mistakes:

• Thinking amount prints as hex
• Assuming amount is undefined
• Confusing toString() usage

4. Identify the error in this JavaScript event listener code for a blockchain contract:

contract.on('Approval', (owner, spender, value) => {
  console.log('Approved:', owner, spender, value.toString);
});

medium

A. contract.on is not a function

B. Wrong event name 'Approval'

C. Callback parameters are incorrect

D. Missing parentheses after value.toString

Solution

1. Step 1: Check usage of toString method

   The code uses value.toString without parentheses, so it logs the function reference, not the string.

2. Step 2: Correct usage requires parentheses

   It should be value.toString() to convert the value to a string for logging.

3. Final Answer:

   Missing parentheses after value.toString -> Option D

4. Quick Check:

   toString() needs () to call method [OK]

Hint: Call toString() with parentheses to convert value [OK]

Common Mistakes:

• Forgetting () after toString
• Assuming event name is wrong
• Misunderstanding callback parameters

5. You want to build a blockchain app that updates user balances automatically when a BalanceUpdated event is emitted by a smart contract. Which event-driven pattern best fits this use case?

hard

A. Event Listener pattern to react and update balances on event emission

B. Command Query Responsibility Segregation (CQRS) to separate reads and writes

C. Event Sourcing to store all balance changes as events

D. Batch Processing to update balances periodically

Solution

1. Step 1: Understand the requirement

   The app must update balances automatically when an event occurs.

2. Step 2: Match the pattern to the need

   The Event Listener pattern listens for events and triggers immediate updates, fitting this use case perfectly.

3. Final Answer:

   Event Listener pattern to react and update balances on event emission -> Option A

4. Quick Check:

   Use Event Listener for automatic reaction to events [OK]

Hint: Use Event Listener to react instantly to blockchain events [OK]

Common Mistakes:

• Confusing Event Sourcing with immediate updates
• Choosing CQRS which separates reads/writes but not event reaction
• Using Batch Processing which delays updates