nodes

Go example for resilient blockchain RPC routing with eznode.

This repo shows how to configure multiple RPC endpoints, set per-node rate limits, prioritize healthy nodes, and send requests through a failover-aware chain abstraction.

What it demonstrates

• Multiple blockchain RPC nodes behind one chain interface
• Per-node request limits (Count / Per)
• Request timeouts for unhealthy endpoints
• Priority-based node selection
• Automatic fallback when a node is down or rate-limited

Quick start

go mod download
go run .

The sample in main.go builds two BSC RPC nodes and sends a request through the EzNode router.

Customize

Edit main.go to change:

• RPC URLs (ChainNodeData.Url)
• Chain identifier (ChainData.Id)
• Rate limits (ChainNodeLimit)
• Health-check interval (CheckTickRate)
• Request path/method (http.NewRequest)

Notes

The checked-in RPC URLs are examples. For production usage, swap them for your own provider endpoints and keep credentials out of git.

Related links

• MeetKai — the operator layer behind Kai CMO workflows.
• KaiCalls — AI voice agents for small-business phone answering and lead capture.
• Connor Gallic — founder building Kai, KaiCalls, and AI automation systems.