How to create a blockchain event
On this page, you’ll learn how to:
-
Create a new blockchain event
-
Register the event in the module
-
Emit the event in the command execution hook
-
Listen to the event. For an example of how to listen to the event, check out the guide How to create a plugin
Blockchain events, or module events, are logs of events that occur in the blockchain network during block execution. Events occur per block, and are stored in the respective block header, from where they can be queried.
By default, a blockchain event is only stored for 300 blocks on-chain, then it is removed, to reduce the overall database size and increase scalability. If desired, the number of blocks for which events are kept in the database can be increased in the node config under |
For the Hello module, we implement a simple blockchain event as an example: The "New Hello" event.
This event should be emitted every time a new "Create Hello" command is executed on a node.
1. Create a new event type
First, define the corresponding interface for the event.
Create a new file called new_hello.ts
inside the events/
folder of the module.
The event data shall contain the address of the sender of the Hello message, and the Hello message which was sent.
export interface NewHelloEventData {
senderAddress: Buffer;
message: string;
}
Define the corresponding schema directly below.
export const newHelloEventSchema = {
$id: '/hello/events/new_hello',
type: 'object',
required: ['senderAddress', 'message'],
properties: {
senderAddress: {
dataType: 'bytes',
fieldNumber: 1,
},
message: {
dataType: 'string',
fieldNumber: 2,
},
},
};
To create the event class, import the BaseEvent
from the klayr-sdk
.
import { Modules } from 'klayr-sdk';
export interface NewHelloEventData {
//...
};
export const newHelloEventSchema = {
//...
};
export class NewHelloEvent extends Modules.BaseEvent<NewHelloEventData> {
public schema = newHelloEventSchema;
}
The new event class is created by extending from the BaseEvent
.
Inside the event class, set the schema of the event data to newHelloEventSchema
, which is defined above.
The BaseEvent
class implements already a method add()
, which can be used to emit the event, so there is nothing else required to be defined in the event.
The schema
property is optional as well, and only required, if the event emits custom data.
Even without schema, it is still possible to signal that something happened, by logging an event.
2. Register the event
Now that we created a new event type, import it into the module.ts
file, and register the event in the module constructor.
import { NewHelloEvent } from './events/new_hello';
// [...]
export class HelloModule extends Modules.BaseModule {
// [...]
public constructor() {
super();
// registration of stores and events
// [...]
this.events.register(NewHelloEvent, new NewHelloEvent(this.name));
}
// [...]
}
3. Emit the event
Now that the event is registered with the module, you can call the add()
method of the event at any time inside the module.
Besides the event data
, topics
are the second property that can be defined by the developer, when emitting/ publishing a blockchain event.
Topics are similar to tags or labels, categorizing the event by a list of the relevant keywords.
The only limitation to what data can be included in the event is the data size:
The maximum size of the event data is 1 kB.
|
Both data
and topics
are passed as parameters to the add()
method of a blockchain event:
In this example, we want to emit the "New Hello" event every time a "Create Hello" command was executed, so we add the corresponding logic at the end of the execute()
command hook.
// [...]
import { NewHelloEvent } from '../events/new_hello';
interface Params {
message: string;
}
export class CreateHelloCommand extends Modules.BaseCommand {
public schema = createHelloSchema;
private _blacklist!: string[];
// eslint-disable-next-line @typescript-eslint/require-await
public async init(config: ModuleConfig): Promise<void> {
// [...]
}
// eslint-disable-next-line @typescript-eslint/require-await
public async verify(context: StateMachine.CommandVerifyContext<Params>): Promise<StateMachine.VerificationResult> {
// [...]
}
public async execute(context: StateMachine.CommandExecuteContext<Params>): Promise<void> {
// [...]
// 6. Save the Hello counter to the counter store.
await counterSubstore.set(context, helloCounterBuffer, helloCounter);
// 7. Emit a "New Hello" event
const newHelloEvent = this.events.get(NewHelloEvent);
newHelloEvent.add(context, {
senderAddress: context.transaction.senderAddress,
message: context.params.message
},[context.transaction.senderAddress]);
}
}
Now, the module will create a new event every time a "Create Hello" command is executed, and the event will include the sender address and the Hello message which has been sent.
An example of how to listen to a specific event, can be found in the guide How to create a plugin. |