Designed for the internet of tomorrow

Radius gives you Ethereum-compatible development patterns with payment-first economics optimized for real-world transaction volume.

What works out of the box

Most Ethereum development workflows transfer directly to Radius.

What differs from Ethereum

Radius is EVM compatible, but it makes deliberate tradeoffs for payment workloads.

Use fixed, predictable fees

Ethereum fees change with demand. Radius uses fixed gas pricing so costs remain predictable.

A standard transaction cost is about 0.00010 USD.

Settle in milliseconds

Use stablecoin-native fee flow

Contract implications

Keep standard Solidity patterns

Your existing contract logic and ERC standards work as expected.

IERC20(token).transfer(recipient, amount);
 
mapping(address => uint256) balances;
balances[msg.sender] = 100;
 
emit Transfer(from, to, amount);

Avoid assumptions tied to Ethereum-native balance semantics

Prefer explicit token accounting over patterns that assume ETH-style native balance behavior inside contract logic.

// Prefer token-based accounting checks in payment flows.
require(IERC20(feeToken).balanceOf(address(this)) > 0);

Data integrity model

Radius prioritizes deterministic execution and replicated operation:

• Three-node clusters provide fault tolerance
• Replication preserves data durability
• Deterministic execution preserves consistency

This model is designed for high-throughput payment infrastructure.

Why this matters for modern applications

AI and machine-to-machine payments

Autonomous systems need low-latency settlement for API calls, inference, and compute usage. Radius supports this with:

• Instant settlement
• Sub-cent transaction costs
• Stable-value fee economics

Micropayment business models

Low predictable cost unlocks:

• Per-request API billing
• Pay-per-visit content
• Streaming payments for compute and bandwidth

EIP support

Radius tracks Prague support through Revm 33.1.0.

Precompiles

Network configuration

Next steps

• Ethereum compatibility — Behavior differences and RPC constraints that affect production systems
• Network and RPC — Endpoints, chain IDs, and integration setup
• Fees — Fee model and the Turnstile behavior