wormhole-explorer/blockchain-watcher
matias martinez 9b57b17be7 changing deployment strategy to jobs per pod 2023-11-15 12:53:05 -03:00
..
config changing deployment strategy to jobs per pod 2023-11-15 12:53:05 -03:00
docs [Blockchain Watcher] Apply missing formatting for log message published (#791) 2023-11-12 19:34:53 -03:00
src Load jobs dinamically 2023-11-15 10:48:39 -03:00
test Load jobs dinamically 2023-11-15 10:48:39 -03:00
.dockerignore Blockchain Watcher: ethereum -> sns implementation (#790) 2023-11-10 09:28:37 -03:00
.gitignore Blockchain Watcher: ethereum -> sns implementation (#790) 2023-11-10 09:28:37 -03:00
.prettierrc.json Blockchain watcher: adding domain and infra layers (#786) 2023-11-07 15:25:06 -03:00
Dockerfile Blockchain Watcher: ethereum -> sns implementation (#790) 2023-11-10 09:28:37 -03:00
README.md [Blockchain watcher] Adding light observability (#793) 2023-11-14 08:08:34 -03:00
TODO.md adding some new abstract types for processor redesign 2023-10-25 10:58:09 -04:00
jest.config.js Blockchain Watcher: ethereum -> sns implementation (#790) 2023-11-10 09:28:37 -03:00
package-lock.json adding 429 handling http client 2023-11-14 09:52:04 -03:00
package.json adding 429 handling http client 2023-11-14 09:52:04 -03:00
tsconfig.json folder rename 2023-10-25 10:03:12 -04:00

README.md

Explorer Event Watcher

The purpose of this process is to watch all Wormhole connected blockchains for events in Wormhole ecosystem contracts, and then produce database records for these events, and other important associated data.

For now, only EVM chains are supported, but this should be readily extensible in the future.

Installation

run npm ci in the root of the project run npm dev in the root of the project

Deployment

This process is meant to be deployed as a docker container. The dockerfile is located in the root of the project.

Configuration

Configuration is loaded from files in config directory. There is a default file, and then a file for each environment. The environment is set by the NODE_ENV environment variable. If NODE_ENV is not set, the default file is used.

Some values may be overriden by using environment variables. See config/custom-environment-variables.json for a list of these variables.

$ NODE_ENV=staging LOG_LEVEL=debug npm run dev

Usage & Modification

A Handler should be created and registered in the handlers directory for each event type that needs to be handled. Handlers are registered inside the src/index.ts file. These handlers are treated as listeners, and thus require 100% uptime to to ensure no events are missed.