Xphere

The v2 whitepaper is the Foundation’s own retrospective. It says version 1.0 used a proprietary smart-contract structure, dropped some transactions and produced blocks irregularly. Those statements explain why the project says it chose EVM compatibility; they are not an independent incident record.

Block zero proves that the documented v2 mainnet was running on February 17, 2025, and chain ID 20250217 embeds that date. The public materials reviewed do not show a migration transaction, a holder snapshot or the point when v1 stopped, so “successor” is more precise than claiming every balance or service was demonstrably replaced.

Xphere divides consensus into two jobs. xpHash miners build the Proof Chain and provide proofs and validator-selection input. Approved Union members run optimized PBFT on the Main Chain, where ordinary transactions are ordered and finalized. Proof of work therefore influences the process but cannot bypass Union admission or finalize a transaction by itself.

The mining protocol is permissionless for supported hardware, yet the current operating guide lists only the IceRiver XP0 and XP Pool. Main Chain participation has a different gate: each Union slot requires 35 million XP and dedicated infrastructure, followed by evaluation by the Foundation and existing Union. Open mining and open finality are separate claims here.

The network began with a CPU software miner and a prior proof-of-work rule. In 2026, xpHash activated at Proof Chain block 1,740,000 without resetting balances or Main Chain history, and specialized IceRiver XP0 hardware replaced the old route.

The change gave Xphere a network-specific mining identity, but it also concentrated practical entry around one ASIC model and one active pool. Nansen's second-quarter review treats xpHash as the period's central technical event; that is evidence of deployment, not proof that hash power is broadly distributed.

The tokenomics page labels 1.5 billion XP as pre-distributed for “XPHERE 1.0 continuity” and schedules up to 4 billion more over 100 years. Rewards mint every 60 blocks and split 40% to miners, 40% to Union and 20% to the Foundation. Fees follow another route: 50% burns, 20% goes to each security group and 10% to the Foundation.

On September 5, 2026, the custom RPC returned total supply of 2,949,612,508.491734752222946935 XP. That is a dated network-state reading, not a table of circulating ownership. The documentation does not publish the original 1.5 billion’s recipient buckets or migration mechanics, and future net supply also depends on minting and the documented burns.

Union Vault is not the protocol's 40% Union allocation. It is a separate, non-upgradeable contract that receives earnings from the Foundation's own Union node, streams a formula-based share to depositors and burns the unused remainder. Exits require a request and a seven-day wait.

Vault parameters can change only after a 48-hour timelock, while the published network vote gives each Union member one vote and the Foundation a tie-break. The unfinished piece is broader governance: holding XP alone neither admits a validator nor gives a binding community vote over future forks.