Skip to content
All projects
PRIVATEPersonal tooling, source not publicPrivate projectInfrastructure

Web3 Automation Toolkit

Personal tooling for wallet monitoring, multi-chain read operations, and Telegram-delivered alerts.

Web3 automation toolkit module layout visualisation
Concept artwork illustrating the architecture. Not a screenshot of a running interface.

Overview

A collection of scripts and small services I built for my own use: watching addresses across chains, normalising what comes back, and pushing anything noteworthy to Telegram.

Problem

Watching activity across several chains by hand does not scale. Each chain exposes a different RPC surface, block explorers rate-limit aggressive polling, and the interesting events are buried in routine ones.

Solution

A polling layer per chain normalises responses into one internal event shape, filters run over that stream to decide what matters, and matches are delivered to Telegram. Adding a chain means adding an adapter, not a new pipeline.

Architecture

Python workers poll RPC endpoints on a schedule and write normalised events to a local store. A filter layer evaluates rules against the stream; a small Node service handles Telegram delivery. Components run as separate containers.

Key features

  • Address monitoring across multiple EVM chains
  • Normalised event shape across differing RPC responses
  • Rule-based filtering for alert-worthy activity
  • Telegram notification delivery
  • Backoff and retry against rate-limited endpoints

Technology stack

PythonNode.jsDockerWeb3.pyTelegram

Current status

Private tooling built for my own workflow. Not packaged for release and not open source, so there is no repository to link.

Links

No public repository or deployment for this project yet, so there is nothing to link here. I would rather leave this empty than point at something that does not exist — happy to talk through the work directly. Get in touch.