A Layer 1 powered by everyday devices
One shared infrastructure behind Phase services.
Low barriers to entry
No initial token stake or dedicated hardware is required to start validating.
Randomized consensus
No one can predict or influence who produces the next block.
Multiple revenue streams
Validators earn PHASE for securing the network and receive additional rewards for serving Phase Proxy traffic.
EVM-compatible from day one
Developers can build applications and deploy smart contracts on Phase.
What Phase Is
Phase was built around a different premise: if the next large wave of participants is mobile-first, the validating layer must be designed for mobile conditions rather than datacenter assumptions.
Phase is not a Proof-of-Stake network and not Proof-of-Work. Validators register with a smartphone and earn their place through demonstrated, on-chain behavior.
Phase is a full Layer-1 blockchain designed to run on smartphones. It combines three core components:
A reputation-based consensus layer.
Validators earn the right to participate by demonstrating reliability over time, not by locking up capital. Registration is a free transaction; there is nothing to stake.A node built for real phones.
A production-grade execution client (built on Reth, fully EVM-compatible), a networking stack designed for devices behind cellular NAT, and a snapshot-first sync path that brings a fresh phone from install to participation in minutes.A mobile proxy layer for AI agents.
The same smartphone nodes that secure the network can double as a network utility: the node ships an opt-in proxy exit (which the mobile build's defaults do not enable), through which AI agents can route traffic and access the web from real mobile-origin connections, with usage metered and settled on-chain.Consensus: Reputation Instead of Stake
Phase uses committee-based BFT consensus (Chained HotStuff). At any given time, a committee of validators collectively produces and certifies blocks. The committee has a budget of 16 voting seats (a client-release parameter, not a function of how many validators register), filled first by the genesis validators — the network's permanent anchors, seated whole in every committee — and then by graduated validators, who hold at most half as many seats as the anchors minus one, so that the anchors alone always form a quorum. With seven anchors the committee seats seven to ten voters with a quorum of five to seven. Votes are aggregated into a compact quorum certificate using BLS signatures, messaging complexity is linear in committee size, and finality is deterministic — a block is final after three chained certificates, seconds after it is produced.
The question the protocol must constantly answer is: which validators should be in the committee? In most blockchains, the answer is determined by how much capital a validator has staked. In Phase, the answer is determined by reputation — a continuously updated score derived entirely from on-chain behavior.
Leadership rotates round-robin among the voting members.
Reputation scoring
Every block records which committee members signed on time and which leader delivered or failed. Those observations accumulate into a per-validator reliability score. The scoring system is designed to be:
Conservative
The score uses a lower confidence bound: a validator with a few perfect votes scores lower than one with hundreds of consistently good votes. Evidence matters, not luck.
Adaptive
Recent performance matters more than distant history, so a validator can recover from a bad patch and a new device can graduate into the system over time.
Stress-aware
The scoring model specifies a correction that distinguishes individual unreliability from systemic outages, so a network-wide failure does not destroy individual reputations; it is specified, not yet active.
Committee selection: deterministic and verifiable
Once per epoch the protocol freezes a selection snapshot: the list of active validators with their reputation-derived weights. Each round's committee is computed from that snapshot by a deterministic function — every node in the network derives byte-for-byte the same committee and can verify the legitimacy of any block's signers. There is no hidden operator choosing who validates.
New validators follow a defined lifecycle: they enter a queue (with a per-epoch admission limit that caps Sybil inflows), serve a probation period in reserved observer seats — signing and earning reputation, but counting toward no quorum and not yet leading — and graduate to full membership once they have accumulated enough evidence of reliability. Graduates then compete, weighted by reputation, for the voting seats beside the anchors. This guarantees newcomers a real path in, without grace periods or special treatment. Leadership rotates round-robin among the voting members.
Rewards only after finality
Validator rewards are released only for heights already finalized under a full quorum, and a payout becomes irreversible as soon as the block that credits it is itself final.
This turns the validator's future income stream itself into skin in the game: the thing at risk is not a deposit, but the earning position built through honest participation.
What happens when a validator misbehaves
There is no slashing — there is no bonded capital to slash. Instead, the protocol's answer to a provable fault is jail and a reputation reset: the validator loses committee eligibility, the income stream that came with it, and the accumulated track record that took months to build. For a long-serving validator this is a substantial economic penalty — and unlike a stake deposit, it cannot be bought back; it can only be re-earned through honest participation.
The fault detector ships today; the automatic jailing step is specified but not yet active, so in the current build the penalty is the score itself — missed votes and failed leadership cost seats, and seats are income.
The cost of misbehavior scales with tenure.
Designed for unreliable validators — because phones are
A committee of phones is not a committee of servers: devices lose signal, switch networks, and run out of battery. Classical BFT protocols simply halt when a third of the committee goes silent. Phase is engineered to degrade gracefully instead:
Built for Real Phones
Mobile validation is not only a consensus problem. It is equally a networking, bootstrap, and storage problem. Phase treats all of them as first-class design targets.
A networking stack built entirely on iroh
Standard blockchain networking assumes a validator is a server: public IP, open ports, stable connectivity. A phone behind carrier-grade NAT, hopping between Wi-Fi and LTE, breaks every one of those assumptions.
Phase replaced the standard Ethereum networking stack entirely with iroh, a modern QUIC-based peer-to-peer transport. Nodes are addressed by cryptographic identity, not IP (dial keys, not IPs); connections are established by NAT hole punching with transparent relay fallback; and the transport layer survives a network switch (Wi-Fi ↔ LTE), so a validator riding the metro does not drop out of consensus. To our knowledge, Phase is the first L1 whose complete networking stack — consensus, block sync, mempool, and state bootstrap — runs over iroh.
Consensus votes, blocks, transactions, and snapshots are all multiplexed over a single QUIC connection per peer: one NAT binding, one handshake, one keepalive — minimal battery and minimal state in the carrier's NAT tables. Beacon nodes relay consensus messages between validators that have no direct path to each other; every proposal and vote is signed end-to-end by its author, and a certificate is the aggregate of those vote signatures, so relays accelerate delivery but cannot forge a single vote.
Snapshot-first sync: minutes, not days
A classical node replays the entire transaction history from genesis — the single biggest reason “a full node on a phone” has been impossible. A Phase node instead downloads the network's current state at a recent finalized block: balances, contract storage, bytecode, and the validator registry, fetched as compressed chunks in parallel from multiple nodes.
The bootstrap is trust-minimized and interruption-proof: the snapshot is chosen by a quorum vote of the Foundation-run beacons, which must agree on both its state root and its full content, and taken only from finalized state; every chunk is cryptographically verified against its manifest, and a beacon that serves a bad chunk is penalized and the chunk fetched again from another beacon when one can take it. Downloads resume from the exact chunk where they stopped, and the import itself is checkpointed: it survives the app being killed, the phone rebooting, or the network disappearing mid-way.
Critically, sync time does not grow with the age of the chain. The network can run for years; a new phone still downloads only the current state — a volume comparable to a large app update.
Full EVM compatibility
Phase's execution layer is built on Reth, a production-grade Ethereum client written in Rust, and exposes a fully EVM-compatible chain (Ethereum fork set through Cancun, with blob-carrying transactions switched off on mainnet). Existing smart contracts, wallets, and developer tooling work out of the box. Consensus and execution are cleanly separated through an internal engine interface — the same architectural split as Ethereum itself, running in a single process on a phone.
Open Questions and Honest Caveats
Phase is under active development, and this litepaper is an introduction, not the authoritative specification.
DOCS ->Phase publishes a full technical whitepaper covering the protocol design in depth; where this document simplifies, the whitepaper governs.