Events and Logging Data
Learn to use events to log information on the blockchain, enabling efficient monitoring and indexing by external applications.
Events and Logging Data is a free Blockchain Smart Contracts with Solidity lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Blockchain Smart Contracts with Solidity learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
What are Solidity Events?
Smart contracts often need to communicate with the outside world. This is where events come in!
Events are a special feature in Solidity that allow your smart contracts to publish information to the blockchain log.
Think of them as notifications that external applications can listen for.
The Power of Event Logs
Events are crucial because directly reading contract state from off-chain applications can be inefficient and costly.
- Cost-Effective: Storing data in events is cheaper than storing it in contract state.
- Indexable History: They provide a historical record of actions, easily searchable by off-chain tools.
- Monitoring: Wallets, explorers, and dApps can "subscribe" to events to react to changes.
Defining Your First Event
Declaring an event is similar to defining a function, but you use the event keyword.
You specify a name for the event and a list of parameters it will carry, just like function arguments.
These parameters define the data that will be logged when the event is emitted.
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;
contract EventExample {
// Declares an event named 'LogMessage'
// It takes a string and a number as parameters
event LogMessage(string message, uint256 timestamp);
}Triggering an Event
Once an event is declared, you can "trigger" it using the emit keyword within any function of your contract.
When emit is called, the event's data is recorded in the transaction's log, but not directly in the contract's storage.
This makes events a lightweight way to signal information.
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;
contract EventExample {
event LogMessage(string message, uint256 timestamp);
function doSomethingAndLog(string memory _msg) public {
// Emits the LogMessage event
// current timestamp is block.timestamp
emit LogMessage(_msg, block.timestamp);
}
}Making Events Searchable
You can add the indexed keyword to up to three event parameters. This makes them searchable and filterable by off-chain applications.
indexedparameters: Stored in a special part of the log called "topics."- Non-
indexedparameters: Stored in the "data" part of the log. - Benefit: Off-chain tools can quickly find transactions related to specific indexed values.
Event with Indexed Parameters
Let's see how to declare and emit an event with an indexed parameter.
Notice how `sender` is marked `indexed`, making it easy to filter for all events from a specific address.
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;
contract IndexedEventExample {
event Transfer(address indexed from, address indexed to, uint256 amount);
function transferTokens(address _to, uint256 _amount) public {
// Imagine some transfer logic here
// Then emit the event
emit Transfer(msg.sender, _to, _amount);
}
}Logs are Not State
It's important to understand that event logs are not stored within the contract's state.
- State: Data stored directly in the contract, readable by other contracts and functions. Expensive.
- Logs: Part of the blockchain's transaction receipts. They are immutable and persistent, but not directly accessible by other contracts. Cheaper.
Events are primarily for off-chain consumption.
Practical Event Applications
Events are used everywhere in smart contracts. Here are some common applications:
- Token Transfers: ERC-20 and ERC-721 standards heavily rely on `Transfer` and `Approval` events.
- Ownership Changes: Notifying when a contract's owner is updated.
- Data Updates: Signalling when important contract variables have changed.
- User Interface Feedback: DApps listen for events to update UI in real-time.
Off-Chain Interaction
While Solidity contracts can't directly read events, off-chain applications (like web dApps) use web3 libraries (e.g., Web3.js, Ethers.js) to:
- Filter Past Events: Query historical blockchain data for specific events.
- Subscribe to New Events: Listen for events as they are emitted in real-time.
This enables powerful, responsive decentralized applications.
Event Concepts Check
Consider the following Solidity event declaration:
event UserRegistered(
address indexed userAddress,
string userName,
uint256 indexed registrationTime
);
Which parameters are indexed and therefore easily searchable by off-chain tools?
Recap: Events & Logging
You've learned about the power of events in Solidity!
- Events are emitted by contracts to log data on the blockchain.
- They are crucial for off-chain monitoring, indexing, and dApp interaction.
- Use the `event` keyword to declare and `emit` to trigger them.
- `indexed` parameters make events easily searchable.
This mechanism is vital for building responsive and data-driven decentralized applications.
Frequently asked questions
Is the “Events and Logging Data” lesson free?
Yes — the full text of “Events and Logging Data” is free to read here on the web, and the Blockchain Smart Contracts with Solidity course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Blockchain Smart Contracts with Solidity course, upgrade to CoddyKit PRO.
What will I learn in “Events and Logging Data”?
Learn to use events to log information on the blockchain, enabling efficient monitoring and indexing by external applications. You practise Blockchain Smart Contracts with Solidity with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Blockchain Smart Contracts with Solidity?
No prior experience is required. Blockchain Smart Contracts with Solidity on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Events and Logging Data” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Blockchain Smart Contracts with Solidity lesson?
Yes. Every Blockchain Smart Contracts with Solidity lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.