Peristiwa dan Data Logging

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.

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.

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.

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.

You can add the indexed keyword to up to three event parameters. This makes them searchable and filterable by off-chain applications.

• indexed parameters: Stored in a special part of the log called "topics."
• Non-indexed parameters: Stored in the "data" part of the log.
• Benefit: Off-chain tools can quickly find transactions related to specific indexed values.

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.

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.

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.

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.

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?

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.