What is Xphere?

XPHERE is an EVM-compatible Layer 1 blockchain designed around a dual-chain architecture. Its Main Chain uses an optimized Practical Byzantine Fault Tolerance (PBFT) process for transaction handling and block finality, while a separate Proof Chain uses the xpHash proof-of-work algorithm to generate cryptographic proofs and support validator selection. The project describes this split as a way to combine fast transaction processing with PoW-backed security and Sybil resistance.

XPHERE 2.0 is the successor to XPHERE 1.0, replacing the earlier proprietary smart-contract model with Ethereum-compatible tooling. The official documentation says Solidity contracts and Ethereum tools can be used without modification, and the homepage targets Cancun-level EVM equivalence. Mainnet uses chain ID 20250217; the testnet uses chain ID 1998991.

The network targets approximately one-second blocks and finality and advertises up to 4,000 transactions per second. The Main Chain's Council/Committee design limits PBFT communication to a randomly selected subset of Union validator nodes, while the Proof Chain is dedicated to proof generation and validator selection rather than ordinary transaction processing.

XP is XPHERE's native asset. It is used for gas, mining rewards, Union validator economics, and Union Vault staking. The project also provides an official explorer (XPScan), a second explorer (Tamsa), ZIGAP wallet integration, mining with IceRiver XP0 hardware after the xpHash upgrade, and a Union Vault staking service.

What problem does Xphere solve?

XPHERE positions itself as a response to the blockchain trilemma: networks often have to trade off scalability, security, and decentralization. The project says its earlier XPHERE 1.0 design had limited accessibility because it used a proprietary smart-contract structure, along with dropped transactions and irregular block generation. XPHERE 2.0 addresses these stated shortcomings with EVM compatibility, deterministic block production, and a redesigned dual-chain architecture.

The design separates transaction finalization from validator-proof generation. A PBFT Main Chain can process and finalize transactions quickly, while the PoW Proof Chain supplies computationally costly proofs and selects eligible validators. Randomized committee selection is intended to reduce communication overhead and make targeted attacks harder, while Union council representation is intended to preserve broader participation.

The economic model is also designed to limit long-run supply growth: emissions decline annually, transaction fees are split with half permanently burned, and the Union Vault burns the portion of its settlement earnings that is not paid to stakers. These mechanisms are intended to provide sustainability and deflationary pressure, although actual economic outcomes depend on network usage, validator/miner participation, and adoption.

How does Xphere work?

XPHERE has two linked chains. The Main Chain handles transactions and finalizes blocks through optimized PBFT. Union validator nodes form a Council; for each consensus round, a smaller Committee is randomly selected to exchange pre-prepare, prepare, and commit messages. Once the Committee reaches consensus, the finalized result is broadcast to the network. Official documentation describes this as reducing traditional PBFT's quadratic all-node communication burden.

The Proof Chain does not process normal transactions. Nodes compete in xpHash proof of work, and valid proofs are used to establish validator eligibility and support the Main Chain. The official docs specify deterministic xpHash activation at Proof Chain block 1,740,000 on mainnet and 327,400 on testnet. Current mining guidance says the xpHash Proof Chain is mined with an IceRiver XP0 ASIC, with rewards sent directly to a targetMiner address without a claim transaction.

XP is minted as a block reward every 60 blocks (about 60 seconds), with the reward reduced by 26.28% each year. The initial schedule lists 2,000 XP per 60 blocks in year one, 1,474.4 XP in year two, and 1,086.93 XP in year three. Minted rewards are allocated 40% to miners, 40% to Union, and 20% to the Foundation.

Transaction fees are separately divided: 50% is burned, 20% goes to Union validators, 20% to Proof Chain miners, and 10% to the Foundation. XP Union Vault staking is distinct from the protocol-level Union allocation: the vault pays stakers from the Foundation Union node's actual earnings, with the docs describing a 60% staker stream and the remainder (more than 40% in the described settlement model) burned. XP has 18 decimals and a 5.5 billion maximum supply, consisting of 1.5 billion carried over from XPHERE 1.0 and 4 billion emitted over 100 years.

Key facts

  • Native token: XP; 18 decimals (1 XP = 10^18 wei).
  • Mainnet chain ID is 20250217; testnet chain ID is 1998991.
  • Dual-chain design: PBFT Main Chain for transactions/finality and xpHash PoW Proof Chain for proof generation and validator selection.
  • Official homepage advertises about 1-second block time/finality and up to 4,000 TPS.
  • Maximum supply is 5.5 billion XP: 1.5 billion pre-distributed continuity supply plus 4 billion emitted over 100 years.
  • Minting occurs every 60 blocks and declines 26.28% annually; year-one reward is listed as 2,000 XP per 60 blocks.
  • Minted reward split: 40% miners, 40% Union, 20% Foundation.
  • Transaction-fee split: 50% burn, 20% Union, 20% miners, 10% Foundation.
  • Mainnet xpHash activation is Proof Chain block 1,740,000; testnet activation is block 327,400.
  • Union validator membership requires a 35,000,000 XP stake, dedicated infrastructure, and Foundation approval, according to the homepage.
  • Official explorers include XPScan (xpscan.io) and Tamsa (xp.tamsa.io); ZIGAP is the documented partner wallet.
  • The homepage identifies XPHERE 2.0 roadmap items as 2025 commercialization, 2026 xpHash hard fork/ecosystem expansion, and planned 2027 real-usage scaling.

Official links

Categories

Related coins

Frequently asked questions

What is Xphere's ticker and what is XP used for?

XPHERE's native token ticker is XP. It pays gas fees, funds mining and Union validator rewards, and is used in Union Vault staking.

Is XPHERE compatible with Ethereum smart contracts?

Yes. The official docs describe XPHERE 2.0 as EVM-compatible and state that Solidity contracts and Ethereum tooling can work without modification; the homepage targets Cancun-level EVM equivalence.

How does XPHERE reach consensus?

The Main Chain uses optimized PBFT with a Council and randomly selected Committees. A separate Proof Chain uses xpHash proof of work to generate proofs and support validator selection; it does not process ordinary transactions.

What is XP's maximum supply?

The maximum supply is 5.5 billion XP. Official tokenomics says 1.5 billion XP was carried over from XPHERE 1.0 and 4 billion XP is emitted as rewards over a 100-year schedule.

How are XP mining and transaction rewards distributed?

Minted rewards every 60 blocks are split 40% miners, 40% Union, and 20% Foundation. Transaction fees are split 50% burn, 20% Union, 20% miners, and 10% Foundation.

How can users inspect XPHERE activity?

Use XPScan at https://xpscan.io or the Tamsa explorer at https://xp.tamsa.io. The official documentation also links the XPHERE public JSON-RPC endpoints and wallet setup guides.

External trackers

Choose a tracking site for Xphere: