VET Transfers

filterTransferLogs(criteria)

The VeChain token VET does not have a contract tied to it, so its transfers must be accessed from a different source.

Using logs.filterTransferLogs gives you access to the transfers, with the same filter options, but the criteriaSet is specifically tailored for transfer events.

Each criteria may include:

• recipient: the address that receives VET

• txOrigin: the address that initiated the transfer transaction

• sender: the address that sent the VET

A sample request with all filters would appear as follows:

// access VET transfers
const logs = await thor.logs.filterTransferLogs({
  options: {
    offset: 0,
    limit: 3,
  },
  range: {
    unit: 'block',
    from: 0,
    to: 20000000,
  },
  criteriaSet: [
    {
      // VET receiver
      recipient: '0x000000000000000000000000000000000000dead',

      // transaction signer/origin
      txOrigin: '0x19135a7c5c51950b3aa4b8de5076dd7e5fb630d4',

      // VET sender
      sender: '0x19135a7c5c51950b3aa4b8de5076dd7e5fb630d4',
    },
  ],
  order: 'asc',
});

Multiple optional criteria can be configured to filter for various addresses.

Type definition and documentation of all options and results:

• Filter Transfer Log Options

• Transfer Logs Result

Example Project

Vechain-energy - Example Snippets - StackBlitzStackBlitz