npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ethereum-event-processor

v5.1.2

Published

Ethereum Event Processor

Downloads

32

Readme

ethereum-event-processor

Description

This module is intended to listen for events that takes place in Ethereum blockchain and act accordingly.

Basically, it polls events from the provided contracts every X milliseconds and executes the corresponding callback for that event passing the event information to it.

Usage

const EthereumEventProcessor = require('ethereum-event-processor');
const Web3 = require('web3');
const web3 = new Web3(new Web3.providers.HttpProvider('http://localhost:7545'));

const options = { pollingInterval: 500, startBlock: 200, blocksToWait: 20, blocksToRead: 20 };
  
const eventProcessor = new EthereumEventProcessor(web3, contract.address, contract.abi, options);

eventProcessor.on('EventName', (event) => {
  console.log(fromBlock, lastBlock); 
});

eventProcessor.on('blocks_processed', (fromBlock, lastBlock) => {
  console.log(fromBlock, lastBlock); 
});

eventProcessor.listen();
eventProcessor.stop();

EthereumEventProcessor

constructor(web3, contract_address, contract_abi options)

Arguments:

web3

A Web3 connection object to the blokchain.

contract_address

The address of the contract to listen for events.

contract_abi

The ABI in JSON format of the contract to listen for events.

options

A JavaScript object containing the configuration for the event processor behaviour.

startBlock Block number to start listening from.

pollingInterval Interval in milliseconds between every poll to the blockchain.

blocksToWait Number of blocks to wait before start reading events from new blocks. This will make the interval to be skipped if (latestBlockNumber - lastReadBlock + blocksToRead) < blocksToWait.

blocksToRead Number of blocks to read in each interval.

listen(options)

Starts or resumes the events processor consuming process. It can receive the same arguments as the constructor options to override default behaviour.

stop

Stop the current event processor consuming process.

on('end', function(fromBlock, toBlock))

Receives a function to be executed every time a new set of blocks is processed. The function receives the start and end numbers of the blocks that have been processed in that iteration.

on(eventName, function(event))

Receives a function to be executed every time the event specified as a string with eventName has been received. The function receives the event object as an argument.