An EVM-equivalent Proof-of-Stake Layer 1 that builds user protection into the chain itself, against lost keys, scams, drained wallets and look-alike addresses. Ethereum tools work unchanged.
Status: Phases 1–2 working locally, public testnet not live yet
The node runs a single-node dev chain or a multi-validator BFT network (Malachite consensus, block sync, transaction gossip, WebSocket subscriptions) on your own machines, and works with MetaMask and Foundry. The user-safety contracts, the TypeScript SDK and the faucet are built and tested. Proof-of-Stake wiring and the public devnet (Phase 3) come next. Testnet tokens (tXDS) have no monetary value and will not convert to mainnet XDS.
Most chains compete on speed and fees. The problems that actually cost ordinary users money are usually left to wallets and apps. xDEVS Chain puts them into the chain.
| Problem users face | Ethereum | Solana | xDEVS Chain |
|---|---|---|---|
| Lost seed phrase = lost funds | Optional smart wallets (ERC-4337) | Wallet-level only | Built-in smart accounts: passkey login, guardian recovery |
| Stolen key drains the wallet | Nothing at protocol level | Nothing at protocol level | Guardian Vault cancel window, plus an opt-in protocol rule (XIP-0001) for existing MetaMask addresses |
| Forgotten unlimited approvals | Unlimited and permanent by default | Delegations persist until revoked | Every allowance expires; one-call "revoke all" |
| Address poisoning, look-alike names | Wallet warnings only | Wallet warnings only | .xdevs names reject look-alikes; recipient checks planned in the RPC |
| Time to finality | About 13 minutes | Seconds | Final on commit (BFT, no reorgs); 1–2 s block time target (public network planned) |
| Developer compatibility | The standard | Different VM | EVM-equivalent: same tools, same Solidity |
All protection features are opt-in and never reverse a finalized transaction. There is no admin key that can freeze or seize anyone's funds. Full comparison and honest trade-offs →
| Feature | Status |
|---|---|
| EVM execution, MetaMask/Foundry-compatible JSON-RPC, local dev chain | Built |
Multi-validator BFT consensus (Malachite), block sync, tx gossip, eth_subscribe, Docker localnet with chaos tests | Built (Phase 2) |
| Smart accounts (passkeys, social recovery, session keys), Guardian Vault, guardian freeze | Contracts built |
Expiring approvals, .xdevs names with look-alike protection, staking & governance contracts | Contracts built |
| EOA lock (XIP-0001) enforced by the node | Built |
| Staking-driven validator set, system contracts in genesis, public devnet, faucet & explorer online | Next (Phase 3) |
| Transaction simulation and recipient-check RPCs, reference wallet | Planned (Phase 4) |
| Encrypted mempool, parallel execution, local fee markets | Planned (Phase 5) |
| Light-client bridges | Planned (Phase 7) |
"Contracts built" means written in Solidity and covered by unit, fuzz and invariant tests in Foundry. They are not yet deployed on any public network and have not been externally audited. See the roadmap.