31 followers
What do you think? …
KraiNode is a browser-only JSON-RPC playground for blockchain devs.
No backend, no saved keys; just pick a chain, run RPC calls, and see responses instantly.
Every Web3 dev has battled flaky endpoints, slow latency, or rate-limits.
KraiNode makes it painless to test providers, measure latency, and debug requests........all in one place.
What’s inside right now:
Connect to Ethereum, Celo, Base, Arbitrum, and more public RPCs (plus custom URLs)
Run any JSON-RPC method with a built-in request editor
See latency stats for every call (auto-timed & stored in History)
Full date/time history of past runs (persisted locally)
Optional custom headers & chain/provider selection
Endpoint “Probe” to check if a provider is live or CORS-blocked
100% client-side; no backend, no key storage
Next up: failover routing, preset templates, and team-level sharing.
Would love feedback. What’s the biggest RPC pain you face while building?
Hey, sounds interesting.
Sounds interesting, Pro tip: you can try to use tools like @PostHog to see how users are interacting with your product. And improve the presentation of your tutorial video with tools like direcstudio.io or screen.studio. That will make it look very professional.
@antrixstar Thank u for the tip
KraiNode is a browser-only JSON-RPC playground for blockchain devs.
No backend, no saved keys; just pick a chain, run RPC calls, and see responses instantly.
Every Web3 dev has battled flaky endpoints, slow latency, or rate-limits.
KraiNode makes it painless to test providers, measure latency, and debug requests........all in one place.
What’s inside right now:
Connect to Ethereum, Celo, Base, Arbitrum, and more public RPCs (plus custom URLs)
Run any JSON-RPC method with a built-in request editor
See latency stats for every call (auto-timed & stored in History)
Full date/time history of past runs (persisted locally)
Optional custom headers & chain/provider selection
Endpoint “Probe” to check if a provider is live or CORS-blocked
100% client-side; no backend, no key storage
Next up: failover routing, preset templates, and team-level sharing.
Would love feedback. What’s the biggest RPC pain you face while building?
Hey, sounds interesting.
Sounds interesting,
Pro tip: you can try to use tools like @PostHog to see how users are interacting with your product.
And improve the presentation of your tutorial video with tools like direcstudio.io or screen.studio. That will make it look very professional.
@antrixstar Thank u for the tip