Events
Last updated
Was this helpful?
Last updated
Was this helpful?
This example used below will utilize the VTHO contract, which manages VeChain's VTHO Token.
Smart Contract Address: 0x0000000000000000000000000000456e65726779
The contract's source code can be found on GitHub at:
Its Application Binary Interface (ABI) is shared on b32, a repository that gathers publicly available interfaces for VeChain projects:
The connection is managed using WebSockets, which connect directly to a VeChain node.
A simple connection can be established with this snippet:
This will receive all events on the blockchain as JSON-encoded strings.
Using the subscriptions
helper, a custom subscription URL can be built that listens only to the specified event:
Filters can be adjusted to only show events that meet specific criteria. These parameters must be indexed
and are given as a list.
The transfer event uses two indexed parameters: from
and to
.
For instance, to filter all transfers originating from a specific address, you would supply that address as the first parameter:
To filter for all transfers to a specific address, provide only the second value in the list:
When using filters, all provided values must match for the filters to apply.
Many contracts emit similar events, which sometimes necessitates restricting listening to a specific contract. An optional options
argument can be used to filter for a particular contract address.
For example, to listen exclusively for VTHO transfers from the VTHO contract at 0x0000000000000000000000000000456e65726779
, it would be defined as follows:
To resume listening from a specific block position, the options can define a blockID
to continue from where a previous listener may have disconnected.
The events are received as JSON-encoded strings. These strings must be parsed and decoded into usable objects.
Using the contract interface defined earlier, you can decode these events with the parseLog()
function:
For additional details on the options, check out the documentation of .
Generic transaction details such as ID, block information, or the origin of the transaction are available in the object as well. Check eventLog.meta
from the example. Learn more about the message type definition in the documentation of .