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

chainsauce

v1.0.20

Published

Source EVM events for easy querying

Downloads

4

Readme


main check

Chainsauce is a general-purpose Ethereum indexer that sources contract events from a JSON-RPC endpoint.

Installation

$ npm install boudra/chainsauce#main

Basic usage

import { createIndexer, createHttpRpcClient } from "chainsauce";
import { erc20ABI } from "./erc20ABI.ts";

// -- Define contracts
const MyContracts = {
  ERC20: erc20ABI,
};

// -- Create an indexer:

const indexer = createIndexer({
  chain: {
    id: 1,
    rpcClient: createHttpRpcClient({
      url: "https://mainnet.infura.io/v3/...",
    }),
  },
  contracts: MyContracts,
});

// -- Attach event listeners:

// subscribe to a specific event
indexer.on("ERC20:Approval", async ({ event }) => {
  console.log("Approval event:", event.params);
});

// subscribe to all events
indexer.on("event", async ({ event }) => {
  console.log("Event:", event.params);
});

// -- Subscribe to deployed contracts:

indexer.subscribeToContract({
  contract: "ERC20",
  address: "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48",

  // optional
  fromBlock: 18363594n,
  toBlock: "latest"
});

// -- One off indexing:

// one off indexing, this will resolve when finished or reject if any error happens
await indexer.indexToBlock("latest");

// -- Continous indexing:

// indexes to the latest block and watches the chain for new events
// until stopped with `indexer.stop()`
// errors will be emitted and will not stop indexing
indexer.on("error", (error) => {
   console.error("whoops", error);
});
indexer.watch();

Event handler types

Event handlers should be automatically inferred when used like this:

indexer.on("ERC20:Approval", async ({ event, context }) => {
  // event is inferred to be an Approval event
  // context is inferred to be the context passed into `createIndexer`
});

But if you need to split out event handler function to other files, you can type them like this;

import { Indexer as ChainsauceIndexer } from "chainsauce";

type MyContext = {
  db: DatabaseConnection
};

const MyContracts = {
  ERC20: erc20ABI,
};

type Indexer = ChainsauceIndexer<typeof MyContracts, MyContext>;

const indexer: Indexer = createIndexer({
   ...
   context: { db: new DatabaseConnection() }
});

async function handleTransfer({
  event, context: { db }
}: EventHandlerArgs<Indexer, "ERC20", "Transfer">) {
  // event is a Transfer event
  // context is a MyContext type
}

indexer.on("ERC20:Transfer", handleTransfer);

How to define ABIs

ABIs in Chainsauce are of type type Abi in abitype.

ABIs must be defined in Typescript if you want automatic typing of events and contract reads, make sure you cast ABIs as const:

const myAbi = [
  ...
] as const;

Factory Contracts

You can subscribe to new deployed contracts in your event handlers by using the function subscribeToContract:

indexer.on("FactoryContract:ContractCreated", async ({ event, context, subscribeToContract }) => {
  subscribeToContract({
    contract: "MyContract",
    address: event.params.contractAddress,

    // optional
    toBlock: "latest"
  });
});

Caching events and contract reads

Chainsauce comes with a cache to speed up reindexing, all you have to do is pass a cache when creating the indexer.

Currently only a SQLite version is available, but other options are planned.

import { createIndexer, createSqliteCache } from "chainsauce";

const indexer = createIndexer({
  cache: createSqliteCache("./chainsauce.db"),
});

Complete examples