Deploy the contracts you already wrote
Standard EVM, chain ID 125, the tooling you use today, and a network that confirms in about a second.
For Solidity teams who want Ethereum compatibility without Ethereum's wait or Ethereum's fees, plus CosmWasm for teams who prefer Rust.
If your contracts compile for Ethereum, they compile for Paxeer X. Point Foundry or Hardhat at chain ID 125, deploy, and your users connect with MetaMask or any EVM wallet they already have. What changes is what they feel: a transaction gets a signed receipt in milliseconds and is final in about a second, for a fee that rounds to nothing.
There is nothing new to learn and nothing to port. Use viem, ethers or web3 as you do today. Standard JSON-RPC answers from sixteen public nodes, and PaxScan verifies your source so users can read what they are signing.
Add the network
Then npx hardhat run scripts/deploy.js --network paxeer and your contract is live, with its receipt back before the command finishes printing. Foundry users pass --chain-id 125 to forge create and carry on. The RPC URL and verification settings are in the developer docs.
What carries over, and what gets better
| On Ethereum today | On Paxeer X | |
|---|---|---|
| Language and compiler | Solidity, solc | Same |
| Tooling | Foundry, Hardhat, viem, ethers | Same |
| Wallets | MetaMask and any EVM wallet | Same, plus PaxPort with passkeys |
| Time to final | Minutes | About a second |
| Fee per transaction | Dollars at busy times | A fraction of a cent, or zero when your app sponsors it |
| Reading state after a write | Wait for the next block | Read pending state the moment your transaction is receipted |
Beyond Solidity
Two more doors are open. Teams who prefer Rust can deploy CosmWasm contracts alongside their EVM ones. And native assets on the network have ERC-20 pointers, so a token issued on the network behaves like an ordinary ERC-20 inside your Solidity, and an ERC-20 you deploy can be held and paid like a native asset.
- Call the network's built-in payment, identity and market functions from Solidity as you would any other contract.
- Sponsor gas for your users so they never hold PAX or see a gas prompt. See gas sponsorship.
- Run the whole network on your laptop in Docker, so your test suite behaves exactly as it will in production.
Run your existing test suite against a local node first. Most teams find it passes unchanged, and the few tests that do not are usually the ones that assumed blocks would be slow.
Related
Deploy in an afternoon
Network details, the verified-contract flow and example repositories, all in one place.