Currently serving active connections from the US & Asia
Kaspa RPC Endpoints
Caribbean's first public Kaspa node operator. Enterprise-grade SSL-secured WebSocket endpoints powered by kaspad v2.0.0 — Toccata ready.
Get API Access
FAQ
Common questions about Real Physics RPC infrastructure.
What is an RPC endpoint?
RPC (Remote Procedure Call) endpoints let your application communicate with the Kaspa blockchain without running your own full node. Connect directly and query balances, submit transactions, subscribe to events, and more.
What is the difference between Borsh and JSON endpoints?
Borsh wRPC (kaspa.realphysics.net) uses binary serialization and is faster — ideal for production apps using the Kaspa Rust SDK or web-sys bindings. JSON wRPC (kaspa-json.realphysics.net) is human-readable and easier to debug — ideal for scripting, testing, or Python/JS clients.
What does --utxoindex mean?
With --utxoindex enabled, the node maintains a full index of all unspent transaction outputs. This allows wallet balance queries, address monitoring, and full UTXO set access — features not available on nodes without this flag.
Is this Toccata ready?
Yes. Our Miami VPS node is already running kaspad v2.0.0, which activates automatically at DAA score 474,165,565 on June 30, 2026. No downtime expected during the fork.
Where are the nodes located?
We operate two nodes: one on a Vultr VPS in Miami, Florida (primary), and one in San Juan, Puerto Rico (Caribbean's first public Kaspa node). Both serve the same SSL-secured endpoints.
How do I get an API key?
During the current launch period, endpoints are open. API key authentication is rolling out soon. Email
info@realphysics.net to reserve your key and lock in current pricing.