Skip to content
xDEVS Chain
TestnetPublic testnet coming soon

The chain thathas your back.

An EVM-equivalent Proof-of-Stake Layer 1 with user protection built into the chain itself. No seed phrases. No instant drains. No forever approvals. No look-alike names.

Read the docsRun a local chainGitHub

01// finality

Final in one block.
No reorgs.

Tendermint-style BFT consensus (Malachite). A block is final the moment validators holding more than two-thirds of the voting power commit it. Nothing to wait out, nothing to roll back.

val-1val-2val-3val-4#18,204final
height 18,204precommits 4/4final

Final on commit

A committed block never reverts. Every block carries a stored commit certificate you can query over RPC.

One validator down? Still final.

Tested: with 1 of 4 validators offline the chain keeps finalizing. With 2 of 4 it halts safely and resumes, with no forks.

Execute, then vote

Validators execute each block before voting on it, so a committed block always comes with the state it produced.

02// guardian vault

A stolen key is not
a drained wallet.

  1. 01 // 02:14

    Someone has your key.

    They sign a transfer of 48,000 tXDS. On most chains, that is the end of the story.

  2. 02 // 02:14

    Above your limit, so it waits.

    Large transfers, approvals and unknown contract calls enter the vault queue for your delay: 24 hours by default.

  3. 03 // 07:40

    Your guardians step in.

    You can cancel on your own. So can the guardians you chose, once enough of them agree.

  4. 04 // 07:41

    Cancelled. Nothing moved.

    And the thief can’t just switch the vault off. Turning protection off waits out the same delay.

Already on MetaMask? XIP-0001 lets an existing address opt into the same protection. If a thief and the owner both hold keys, guardian freeze breaks the stalemate.

03// passkeys

No seed phrase.
Just you.

Accounts on xDEVS Chain can be smart accounts secured by a passkey on your own device. The chain checks the signature natively, so there is no private key to copy, store or leak.

  • Passkey login

    Face ID, a fingerprint or a security key. Nothing to write down, nothing to lose in a drawer.

  • Social recovery

    Lose your phone and the guardians you chose approve a new key, after a delay you can cancel.

  • Session keys

    Give a game or app a key with a time window and spend caps, never the keys to everything.

How smart accounts work

04// approvals & names

Approvals that expire.
Names that can’t be faked.

Every allowance has an end date.

XDRC-20 tokens and the Permit2Expiring contract put an expiry on every approval, even “unlimited” ones. When it passes, the allowance reads zero. One call revokes them all.

Expiring approvals

Look-alikes can’t register.

While paypal.xdevs exists, nobody can claim paypa1.xdevs. Confusable characters share one skeleton, and non-ASCII homographs are refused outright.

XNS names

05// evm-equivalent

Your tools.
Unchanged.

revm with Ethereum’s Osaka rules. Hashes, receipts and state roots are computed the Ethereum way. If it runs on Ethereum, it runs here.

  • Solidity
  • Foundry
  • Hardhat
  • viem
  • ethers
  • MetaMask

EIP-1559 · EIP-2930 · EIP-7702 · P256VERIFY

Deploy a contract
zsh
$ xdevs run --dev
# chain id 7117 · JSON-RPC on 127.0.0.1:8545
$ cast chain-id --rpc-url $RPC
7117
$ forge create src/Counter.sol:Counter \
$   --rpc-url $RPC --private-key $PK --broadcast
Deployer:    0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266
Deployed to: 0x5FbDB2315678afecb367f032d93F642f64180aa3
$ cast call 0x5FbD…0aa3 "number()(uint256)" --rpc-url $RPC
0

06// measured

Measured,
not promised.

A 5-hour soak of a 4-validator network under load. Every number here comes from a real run, not a projection.

Soak test under load
5h
Validators, BFT consensus
4
Block time during the soak
1s
Transactions
360,000
Forks
0
State-root mismatches
0
422
Rust tests
340
Contract tests
1 of 4
Validators offline, still finalizing

No TPS claims. Throughput and finality benchmarks on reference hardware will be published with Phase 5.

07// roadmap

Built in the open.
Shipped in phases.

Phases 1 and 2 are built and tested. The public testnet is not live yet; it comes with Phase 3. Dates aren’t promised. Progress is.Full roadmap

  1. P1

    Single-node chain

    EVM execution, JSON-RPC, MetaMask and Foundry.

    Built
  2. P2

    BFT network

    Malachite consensus, block sync, gossip, WebSockets.

    Built
  3. P4

    Safety layer RPCs

    Simulation and recipient checks, reference wallet. Contracts already built.

    Planned
  4. P5

    Performance & MEV

    Encrypted mempool, parallel execution, local fee markets.

    Planned
  5. P6

    Public testnet

    Long-lived testnet, independent validators, bug bounty.

    Planned
  6. P7

    Interop

    Light-client bridges only, audits, mainnet preparation.

    Planned

Build on the chain
that has your back.

Run a 4-validator network on your laptop today. The public testnet is coming soon.

Run a local chainRead the docs