v0.1.1

🔄 JSON-RPC Proxy v0.1.1 Release

We're pleased to announce the release of JSON-RPC v0.1.1, which introduces important privacy improvements for configuration management.

What's New in v0.1.1

• Named URL Routes: Added support for human-readable names in route configurations
• Privacy Protection: Prevent sensitive API keys from appearing in logs
• Improved Logging: Logs now show friendly endpoint names instead of full URLs
• Batch Processing Fix: Fixed type handling in batch request processing

Configuration Update

The configuration format now supports named routes:

default_url: "https://mainnet.infura.io/v3/your-project-id"
default_name: "Infura Mainnet"
routes:
  - method: "eth_chainId"
    url: "https://polygon-rpc.com"
    name: "Polygon RPC"
  
  - method: "eth_blockNumber"
    url: "https://rpc.ankr.com/eth"
    name: "Ankr Ethereum"

Why This Matters

Many RPC endpoints require API keys in the URL. With this update, these sensitive credentials no longer appear in your logs, improving security and making logs more readable.

Upgrading

This is a backward-compatible change. Existing configurations without names will continue to work, but we recommend adding names to your routes for improved security and readability.

# Pull the latest version
docker pull ghcr.io/omegatymbjiep/jsonrpc-proxy:latest