Skip to content

Repository files navigation

XPHERE Documentation

Source for the official XPHERE documentation at docs.x-phere.com.

XPHERE is an EVM-compatible Layer 1 with a dual-chain architecture: a PBFT Main Chain for fast finality and an xpHash Proof-of-Work Proof Chain for validator selection and security.

What's here

Section Covers
Developers Quickstart, wallet setup, smart contracts, token standards, EVM compatibility
References Network parameters, public RPC endpoints, JSON-RPC and xp_* method reference
Nodes Running an Endpoint Node (XEN), CLI, chaindata snapshots, validator requirements
Mining xpHash mining and rewards
Staking XP Union Vault — settlement model, fees, risks, contracts
Union The validator group: role, requirements, members
Ecosystem Grant program and ecosystem directory
Resources FAQ, glossary, tokenomics, security, network upgrades

The whitepaper covers the architecture, consensus, and economic model.

Node downloads

The XEN node package is published from this repository and served at docs.x-phere.com/nodes/downloads, with a SHA256 checksum alongside it.

Running locally

Requires Node.js ≥ 18.

npm install
npm start          # dev server with live reload at http://localhost:3000
npm run build      # production build into build/
npm run serve      # serve the production build locally

The build fails on broken internal links (onBrokenLinks: "throw"), so a successful build means every internal link and anchor resolves.

Contributing

Corrections are welcome — accuracy matters more here than completeness.

Everything must be verifiable. Network values, RPC responses, contract addresses, and command output should be checked against the live network or the client source before being documented. If a fact cannot be verified, the docs say so rather than guessing. For example:

# Confirm a chain ID before documenting it
curl -s -X POST https://en-hkg.x-phere.com \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Open an issue or a pull request. For anything security-related, do not open a public issue — email security@x-phere.com (see Security).

Links


© XPHERE Foundation

About

No description, website, or topics provided.

Resources

Security policy

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages