Network Telemetry

Live diagnostic feed from Kairo Vault's XRPL infrastructure. Public WebSocket on wss://ws.kairovault.com — direct xrpl.js connection, no API key. Tokyo-hosted, validator peer protocol. No middleware.

LIVE · refresh 5s

XRPL Mainnet

Network ID: —

UNKNOWN

Peers

—

Uptime

—

Complete Ledgers

—

Node Public Key

—

Version

—

Load Factor

—

Quorum

—

Fee Base

—

Authenticated Endpoint

https://xpop.kairovault.com/api/v1/rpc/xrpl

Public WebSocket

Direct xrpl.js connection · no API key

PUBLIC

WebSocket Endpoint

wss://ws.kairovault.com

Use From

xrpl.js · Python xrpl-py · raw WebSocket clients

Available Subscriptions

ledger · transactions · validations · server

Protocol

Port

6005

Auth

none

Tier

all

Notes

Direct peer access for AI agents and developers. Anonymous, rate-limited at the host level. For authenticated JSON-RPC + XPoP retrieval, use the gateway endpoints.

▣ Host Infrastructure

Public Endpoint

xpop.kairovault.com

Provider

Contabo Asia · 24 GB RAM · NVMe

Location

Tokyo, Japan

Tunnel

Cloudflare · NRT12 POP · QUIC

TOKYO

Technical Reference

Documentation for AI agents and developers building on this infrastructure.

⚙ Server Configuration

rippled is deployed on a 24 GB Contabo VPS in Tokyo. Memory and storage are tuned for steady-state operation with public WebSocket exposure (wss://ws.kairovault.com) on top of validator peer protocol.

Node Size: medium. Caps the memory caching footprint inside rippled.cfg.
Ledger History: online_delete=256 to purge historical ledgers and prevent storage exhaustion.
Docker Image: xrpllabsofficial/xrpld running latest mainnet rippled.
Gateway: kong:3.9 (DB-less) authenticates + rate-limits all client traffic. cloudflared provides TLS termination via Cloudflare Tunnel.

⌬ Endpoint Mapping

Network	Protocol	Host Port	Internal/Public	Notes
XRPL	WS	8081	Locked (gated via API)	Direct WebSocket — only Kairo Vault gateway can reach it
XRPL	JSON-RPC	5005	Internal only	Admin port (127.0.0.1)
XRPL	WS	6005	Public	Public WebSocket — direct xrpl.js / Python connection · wss://ws.kairovault.com
XRPL	PEER	51235	Public	Validator peer protocol — required for chain connectivity
Gateway	HTTPS	443	Authenticated	xpop.kairovault.com · X-API-Key required for /api/v1/* (telemetry exempt)

{ } API Usage Examples

Public WebSocket (no key, direct xrpl.js):

# Subscribe to ledger close + validation streams from any xrpl.js client
import { Client } from 'xrpl';
const client = new Client('wss://ws.kairovault.com');
await client.connect();
await client.request({ command: 'subscribe', streams: ['ledger', 'validations'] });

Public telemetry (no key required):

# curl the public telemetry endpoint — same data as this page
curl https://xpop.kairovault.com/api/v1/telemetry/xrpl

Authenticated JSON-RPC (X-API-Key required, tier-pro+):

# Look up an account on the network
curl -X POST https://xpop.kairovault.com/api/v1/rpc/xrpl \
  -H "Content-Type: application/json" \
  -H "X-API-Key: <your-api-key>" \
  -d '{"method":"account_info","params":[{"account":"r..."}],"id":1}'

XPoP retrieval (X-API-Key required, all tiers):

# Get an XLS-41d Proof of Payment for any tx hash
curl https://xpop.kairovault.com/api/v1/xpop/<tx_hash> \
  -H "X-API-Key: <your-api-key>"