Chain Listener SDK
A universal multi-chain distributed blockchain listener SDK that provides reusable multi-chain monitoring capabilities. The SDK focuses on asynchronous blockchain event listening and data processing, offering flexible solutions for different business scenarios.
Features
- Universal Multi-Chain Support: Ethereum, BSC, Polygon, Arbitrum, Optimism, Avalanche, Solana, TRON, Kava, Osmosis, Base
- Distributed Architecture: Support for multi-instance deployment with automatic load balancing
- Event-Driven: Callback-based event processing with user-defined handlers
- Fault Tolerant: Automatic failover and recovery mechanisms
- High Performance: Async/await architecture with efficient event processing
- Flexible Deployment: From simple standalone to distributed cluster
Quick Start
Codex Skill
This repository now includes a Codex skill bundle at
codex-skills/chain-listener-event-ops.
- Analyst workflow: generate JSONL/CSV capture listeners for on-chain event sampling and downstream analysis
- Developer workflow: generate event consumer scaffolds for callback-based integrations
Example scaffold command:
poetry run python codex-skills/chain-listener-event-ops/scripts/scaffold_listener.py \
--persona analyst \
--chain-name bsc \
--chain-type bsc \
--contract-name USDC \
--contract-address 0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d \
--abi-path examples/bsc_usdc_transfer_listener/usdc_erc20_abi.json \
--event Transfer \
--output examples/generated/bsc_usdc_transfer_capture.py
To make the skill globally available in Codex, copy or symlink the skill folder
into $CODEX_HOME/skills/.
Documentation
Development
Setup
# Install Poetry
pip install poetry
# Install dependencies
poetry install
# Activate virtual environment
poetry env activate
Code Quality
# Format code
black src/ tests/
# Type checking
mypy src/
# Linting
flake8 src/ tests/
License
[License Name]
Contributing
Please read our contributing guidelines and code of conduct before submitting pull requests.
Metadata
Release files for chain-listener 0.2.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| chain_listener-0.2.12.tar.gz | 47.1 kB | Without provenance | Details for chain_listener-0.2.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chain_listener-0.2.12-py3-none-any.whl | Python 3 | none | any | Details for chain_listener-0.2.12-py3-none-any.whl |
Total release size: 105.7 kB
Release files / chain_listener-0.2.12.tar.gz
| Download URL | chain_listener-0.2.12.tar.gz |
|---|---|
| Size | 47.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
631838de382de5ed94887e74edd5960a3a51227da0d13529ad7ce599d275d875
|
|
BLAKE2b-256 checksum How to use checksums |
8928efa17cb080df3be19f8a133a8161ce6dfc477e0c450ab596f48ca6f16ce1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.14.0 Darwin/25.1.0
|
Release files / chain_listener-0.2.12-py3-none-any.whl
| Download URL | chain_listener-0.2.12-py3-none-any.whl |
|---|---|
| Size | 58.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dc0b9480a0ec8b075f968ff30bc240c40ab4dcb800486654ee27000f457a7af6
|
|
BLAKE2b-256 checksum How to use checksums |
a05c52abe342fc99d12848c8856ce5b471132a241c200efdf7adfd92813f5919
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.14.0 Darwin/25.1.0
|
Security for chain-listener 0.2.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.