Product · Open source
One line to install, full coverage to build with
pip install evrmore-rpc — then talk to your Evrmore node from Python with type hints, connection pooling, ZMQ notifications, and intelligent asset decoding.
Under the Manticore Technologies umbrella we build infrastructure and tooling for decentralized systems. The Evrmore blockchain is one of the chains we care about: a Bitcoin-derived chain with native assets, smart contracts, and a growing ecosystem. To build wallets, explorers, indexers, or game engines on top of it, you need a reliable way to talk to an Evrmore node. That’s what evrmore-rpc is for.
It’s not just a thin RPC wrapper. It’s a full developer toolkit: context-aware (works identically in sync and async code), flexible configuration (evrmore.conf, env vars, or manual args), full method coverage with type hints and structured responses, connection pooling for low-latency concurrent calls, ZMQ support for real-time blockchain events with auto-decoding, and intelligent parsing of asset transactions. We’ve stress-tested it and documented it; it’s ready for production use.
Install and run
evrmore-rpc on PyPI — install with:
pip install evrmore-rpcOptional extras:
pip install evrmore-rpc[websockets] # WebSocket support
pip install evrmore-rpc[full] # All optional dependenciesQuick start:
from evrmore_rpc import EvrmoreClient
client = EvrmoreClient() # auto-loads from evrmore.conf
info = client.getblockchaininfo()
print("Height:", info['blocks'])
print("Difficulty:", info['difficulty'])
If you don’t have evrmore.conf, you can pass URL, user, password, port, and testnet flag directly, or set env vars (EVR_RPC_URL, EVR_RPC_USER, EVR_RPC_PASSWORD, etc.). Cookie auth from ~/.evrmore/.cookie is also supported.
Sync and async, same API
The client is polymorphic: it detects whether you’re in sync or async context and behaves accordingly. Same methods, no separate AsyncClient. In an async function you await the same calls; in sync code you don’t. No context managers required—just create the client and use it. When you’re done, call client.close() (or await client.close() in async).
RPC, ZMQ, and assets
You get full coverage of Evrmore RPC methods with typed parameters and structured responses (including Pydantic-style models where it helps). For real-time updates, the ZMQ client lets you subscribe to block and transaction notifications with optional auto-decoding: raw hashes, raw blocks/tx, or decoded blocks and transactions with asset metadata. Asset operations—get asset data, transfer assets—are first-class. The library handles the boilerplate so you can focus on your app logic.
Built for production
We’ve run stress tests against local and remote nodes; the client supports connection pooling for high throughput. The codebase is tested, linted, and documented. There are examples for basic queries, async usage, asset operations, ZMQ with auto-decode, cookie auth, connection pooling, and full RPC coverage checks. If you’re building something on Evrmore—a wallet, an explorer, a game economy, an indexer—evrmore-rpc is there to save you time and keep your code clean.
Try it
Install from PyPI → evrmore-rpc. Full docs, API reference, and examples are in the project repo. I’m surprised this hasn’t gotten more attention yet—if you’re into Evrmore or building on Bitcoin-style chains with assets, give it a look and reach out if you hit anything we can improve.