XPHERE Endpoint Node
An Endpoint Node — XEN — is how an application reaches the XPHERE network. It holds a full copy of the chain, answers queries locally, and relays the transactions you submit to its peers.
Who needs one
You do not need to run a node to build on XPHERE. The public endpoints are enough to get started, and for many applications they are enough permanently.
Run your own Endpoint Node when you want:
- No shared rate limit — public endpoints are shared infrastructure.
- Namespaces the public endpoints do not serve —
debug_*,admin_*, andpersonal_*are not exposed publicly. See JSON-RPC APIs. - Independence — your service keeps working if a third-party provider has an outage, and you are not trusting anyone else's view of the chain.
- Archive or indexing workloads — heavy historical queries that would be throttled elsewhere.
What it does
- Synchronizes blockchain data from its peers.
- Validates every block it receives, rather than trusting what it is told.
- Answers state and history queries over JSON-RPC.
- Propagates the transactions it receives to the rest of the network, so they reach the Union members who propose blocks.
An Endpoint Node does not propose or seal blocks. Block production is split between Union validators, which finalize on the Main Chain, and miners, who seal Proof Chain blocks.
What ships in the package
| Interface | Purpose |
|---|---|
| JSON-RPC server | Ethereum-compatible eth_* / net_* / web3_* plus the XPHERE-specific xp_* namespace, over HTTP, WebSocket, and IPC |
| Command-line interface | bin/xen for node operation and account management, plus an interactive JavaScript console that attaches to a running node |
The published package is a single Linux x86-64 build. See Requirements for what it runs on.
Next steps
- Requirements — hardware, OS, and disk sizing
- Install XEN — download, configure, and start the node
- Chain Data Snapshots — skip the initial sync
- CLI commands — operating the node
- JSON-RPC APIs — exposing and securing the RPC interfaces