DEVELOPERS

Build with tools
you already know.

Standard JSON-RPC, Solidity, Foundry, viem, ethers, and familiar wallets. Pons-specific primitives remain composable contracts—not a closed runtime.

RPCrpc.pons-l3.network
Chain ID7333
CurrencyPONS
EnvironmentPublic devnet
QUICKSTART 01

Add the network

The public development network accepts standard Ethereum JSON-RPC requests and can be added directly to MetaMask or another EVM wallet.

Network namePons L3 Devnet
RPC URLhttps://rpc.pons-l3.network
Chain ID7333
Currency symbolPONS
Chain ID (hex)0x1ca5

JSON-RPC

The public gateway forwards safe Ethereum JSON-RPC methods to the development execution node. It blocks administrative namespaces, validates request sizes, rate-limits abusive clients, and exposes separate health data for the status page.

request
curl https://rpc.pons-l3.network \
  -H "content-type: application/json" \
  --data '{
    "jsonrpc":"2.0",
    "id":1,
    "method":"eth_chainId",
    "params":[]
  }'
Public devnet onlineHTTPS JSON-RPC

Foundry

Foundry works through the standard RPC surface. Deployment keys remain local; the network never asks developers to upload them.

foundry
export PONS_L3_RPC=https://rpc.pons-l3.network

cast chain-id --rpc-url $PONS_L3_RPC

forge script script/Deploy.s.sol:Deploy \
  --rpc-url $PONS_L3_RPC \
  --broadcast

viem

typescript
import { defineChain } from 'viem'

export const ponsL3 = defineChain({
  id: 7333,
  name: 'Pons L3 Devnet',
  nativeCurrency: { name: 'Pons', symbol: 'PONS', decimals: 18 },
  rpcUrls: {
    default: { http: ['https://rpc.pons-l3.network'] }
  }
})

Core contracts

Rollup, bridge, inbox, outbox, sequencer inbox, native-token bridge, and Pons application contracts will be published together. Addresses are never added incrementally from memory: they come from the signed deployment manifest.

Public RPC policy

  • HTTPS JSON-RPC at one stable public hostname.
  • Batch requests accepted within bounded request sizes.
  • admin_*, personal_*, miner, and node-management methods blocked.
  • Expensive tracing methods disabled on the public tier.
  • Short caching for immutable and commonly repeated reads.
  • Per-IP limits with higher authenticated tiers added only if demand requires them.
Copied