Web3 & DApp Development Fundamentals · Lección

Declaración de eventos

Emitir registros on-chain

Declaración de eventos es una lección gratuita de Web3 & DApp Development Fundamentals en CoddyKit. Esta es la lección 1 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Web3 & DApp Development Fundamentals, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Web3 & DApp Development Fundamentals incluye 4 lecciones en total.

Partes de esta lección aún no han sido traducidas y se muestran en inglés.

What Are Events?

Events let a smart contract write entries to the blockchain's log. These logs are a cheap way to record that something happened and are the primary channel for contracts to communicate with off-chain applications.

Front-ends, indexers, and analytics tools all listen for events.

Declaring an Event

You declare an event with the event keyword and a list of typed parameters. The declaration defines the event's shape.

<code>event Transfer(address from, address to, uint256 amount);</code>

Emitting an Event

To fire an event you use the emit keyword followed by the event name and arguments. This appends a log entry to the transaction receipt.

<code>function send(address to, uint256 amount) public {
    // ... transfer logic
    emit Transfer(msg.sender, to, amount);
}</code>

Why Use Events?

Events solve two problems:

Cheap record-keeping - logs cost far less gas than storage
Off-chain communication - dApps cannot read storage in real time, but they can subscribe to events

Contracts themselves cannot read their own emitted events, however.

A Complete Example

Here is a small contract that emits an event whenever a value is updated, so any listening app knows the change immediately.

<code>contract Counter {
    uint256 public count;
    event Incremented(uint256 newCount);

    function increment() public {
        count += 1;
        emit Incremented(count);
    }
}</code>

Logs Are Not Storage

Event data is stored in a special log area of the transaction receipt, not in contract storage. This is why they are cheap, but it also means the contract cannot query past events on-chain.

Logs are accessible to off-chain clients and block explorers.

Naming and Conventions

By convention events are named with PascalCase and often describe a past action: Transfer, Approval, Deposit, OwnershipTransferred.

Standard interfaces like ERC-20 define required events you must emit.

<code>event Approval(address owner, address spender, uint256 value);
event Deposit(address account, uint256 amount);</code>

Multiple Parameters

Events can carry several parameters of any type, including string and bytes. The data is ABI-encoded into the log.

<code>event OrderPlaced(uint256 id, address buyer, string product, uint256 price);

function place(uint256 id, string memory p, uint256 price) public {
    emit OrderPlaced(id, msg.sender, p, price);
}</code>

Gas Cost of Events

Emitting an event costs gas, but much less than writing the same data to storage. The base cost plus a small per-byte fee makes events the preferred way to expose historical data.

Rule of thumb: store what the contract needs to read, emit what off-chain apps need to read.

Events in the ABI

Event declarations appear in the contract's ABI so that client libraries know how to decode the logs. The event signature is hashed to create a topic identifier.

<code>// ABI entry (simplified)
// { type: 'event', name: 'Transfer',
//   inputs: [from, to, amount] }</code>

Events for State Changes

A best practice is to emit an event for every meaningful state change. This gives applications a reliable, ordered history they can replay to rebuild state.

<code>address public owner;
event OwnerChanged(address previous, address next);

function setOwner(address next) public {
    emit OwnerChanged(owner, next);
    owner = next;
}</code>

Quick Check

Test your understanding of declaring events.

Recap

You learned how to declare and emit events:

Declare with event Name(types...)
Fire with emit Name(args...)
Logs are cheap, off-chain readable, and not queryable on-chain
Emit an event for every meaningful state change

Events are the bridge between your contract and the outside world.

Preguntas frecuentes

¿La lección «Declaración de eventos» es gratis?

Sí — el texto completo de «Declaración de eventos» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Web3 & DApp Development Fundamentals, actualiza a CoddyKit PRO. El curso de Web3 & DApp Development Fundamentals incluye 4 lecciones en total.

¿Qué aprenderé en «Declaración de eventos»?

Emitir registros on-chain Practicas Web3 & DApp Development Fundamentals con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.

¿Necesito experiencia previa para empezar Web3 & DApp Development Fundamentals?

No se requiere experiencia previa. Web3 & DApp Development Fundamentals en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 1 de 4.

¿Cuánto tiempo toma la lección «Declaración de eventos»?

La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.

¿Puedo escribir y ejecutar código en esta lección de Web3 & DApp Development Fundamentals?

Sí. Cada lección de Web3 & DApp Development Fundamentals incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.

Todas las lecciones de este curso

← Volver a Web3 & DApp Development Fundamentals