Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Designed for the Internet of Tomorrow

EVM-compatible with different economics and architecture. Deploy Solidity contracts unchanged, use Foundry and viem.

What works

Your existing Ethereum development workflow transfers directly to Radius:

Tool/FrameworkStatus
SolidityFully supported (Validated up to Prague)
wagmiCompatible
viemCompatible
OpenZeppelinCompatible
FoundryCompatible
Standard precompilesCompatible (Validated up to Prague)

What's different from other EVMs

Radius optimizes for payments. This means deliberate differences from standard Ethereum behavior:

Predictable fees (not market-dependent)

Traditional blockchain fees fluctuate with network demand. Radius charges a fixed 0.0001 USD per transaction—predictable, auditable, and calculable.

Stablecoin Fees

EthereumRadius
Fees paid in ETHFees paid in stablecoins (USD)
Must hold native tokenNo separate gas token needed
eth_gasPrice returns market rateReturns 9.8599881e-11 (0.0001 USD)

Faster Finality

EthereumRadius
~12 minutes for high confidenceImmediate
12+ confirmations recommended0 confirmations needed
Reorgs possibleNo reorgs

Key Differences from Ethereum

FeatureEthereumRadius
Fee modelMarket-based (ETH bids)Fixed 0.0001 USD
Settlement time12+ minutesInstant (milliseconds)
Failed txsCharge gas even if revertedCharge only on success
Required tokenMust hold ETHOptional (stablecoins work)

Practical Implications

Your contracts work unchanged:
// Standard ERC-20 interactions
IERC20(token).transfer(recipient, amount);
 
// Storage operations
mapping(address => uint256) balances;
balances[msg.sender] = 100;
 
// Events
emit Transfer(from, to, amount);
Avoid native balance patterns:
// Don't do this (always returns 0)
require(address(this).balance > 0);
 
// Do this instead
require(IERC20(feeToken).balanceOf(address(this)) > 0);

How Radius ensures data integrity

Radius uses operator trust + replication rather than decentralized consensus:

  • 3-node clusters provide fault tolerance (operator nodes replicate data)
  • Cryptographic signing prevents tampering
  • Deterministic execution ensures consistency

This trade-off (known operators for instant finality) is appropriate for payment infrastructure.

Future-Proofing

Real-time autonomous payments

AI agents need to pay for services (APIs, data, compute) instantly. Traditional payment processors require 30+ day settlement. Radius provides:

  • Instant settlement — Agent gets confirmation in milliseconds
  • Sub-cent costs — Enables per-request pricing
  • Stablecoin support — Agents don't need volatile assets

Micropayments

When transactions cost $0.0001, new business models become viable:

  • Per-request API billing: Charge per call, not monthly
  • Content micropayments: Pay per article, not subscription
  • Streaming payments: Pay by the second for compute

Traditional payment processors (Stripe, PayPal) can't economically support these patterns. Radius can.

EIP Support (Prague)

Radius tracks the Prague hardfork via Revm 33.1.0:

EIPSupport
EIP-7702Set EOA account code
EIP-1559Fee market (adapted for stablecoins)
EIP-2930Access lists
EIP-4844Blob transactions

Precompiles

All standard precompiles plus Radius extensions:

AddressPrecompile
0x01 - 0x0aStandard Ethereum precompiles
0x4Db27Fa...Radius Edge (external data)
0x07a2bA2...Debug utilities

Network Configuration

Network Name: Radius Testnet
RPC URL: {TESTNET_RPC_URL}
Chain ID: {TESTNET_CHAIN_ID}
Currency Symbol: {NATIVE_TOKEN}

Next Steps