What is the Katana RPC URL?

The Katana Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/katana. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 747474.

How do I add Katana to MetaMask?

Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC Katana, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/katana, Chain ID: 747474, Currency Symbol: ETH.

Is Katana EVM compatible?

Yes. Katana is fully EVM compatible. Solidity contracts deploy without modification and standard Ethereum tooling works out of the box. Only the RPC URL and Chain ID (747474) change.

What makes Katana different from other DeFi chains?

Katana concentrates liquidity in a curated set of core protocols instead of hosting hundreds of competing deployments, and it routes bridged assets into productive yield by design.

What gas token does Katana use?

Katana uses ETH for gas. Transaction fees are paid in ETH like on Ethereum and most of its Layer 2 ecosystem.

Why do public Katana RPCs fail in production?

Public Katana endpoints are shared infrastructure serving many applications simultaneously. Under load they rate-limit requests, return stale block data, and drop WebSocket connections. Production applications need a dedicated provider.

Does BoltRPC support WebSocket for Katana?

Yes. BoltRPC provides WebSocket endpoints for Katana at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/katana. Use WebSocket for real-time event streaming: new blocks, pending transactions, contract event logs.

Katana RPC Endpoint

Katana is the DeFi-first chain in the Polygon ecosystem, built around concentrated liquidity and productive TVL. A dedicated endpoint keeps your strategy in sync.

chain id · 747474JSON-RPC 2.0WebSocketDebug

Start free trial Contact sales

LIVE LATENCY

20ms

LIVE

gateway round-trip · sampled every second

IN PRODUCTION AT Chainlink

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/katana

WEBSOCKET

wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/katana

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider(
  "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/katana"
);

const blockNumber = await provider.getBlockNumber();
console.log("Latest block:", blockNumber);

import { createPublicClient, http, defineChain } from "viem";

const katana = defineChain({
  id: 747474,
  name: "Katana",
  nativeCurrency: { name: "Ether", symbol: "ETH", decimals: 18 },
  rpcUrls: {
    default: { http: ["https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/katana"] },
  },
});

const client = createPublicClient({ chain: katana, transport: http() });

curl https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/katana \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Connect your dApp, bot, or protocol to Katana Mainnet with BoltRPC. Katana is the DeFi-focused chain in the Polygon ecosystem, built to concentrate liquidity in a curated set of core protocols, and predictable request-unit pricing keeps your RPC bill flat while your strategies run around the clock.

Chain at a Glance


Chain ID	747474
Protocol	EVM chain in the Polygon ecosystem, Agglayer-connected
Block time	~1 second
Gas token	ETH
Settlement	Ethereum (via the Agglayer)
EVM compatible	Yes

What Katana is Built For

Katana takes the opposite approach to most general-purpose chains: instead of hosting hundreds of competing forks, it concentrates liquidity in a small set of core DeFi protocols, lending, spot and perps, and routes bridged deposits into productive yield by design. Launched in 2025 within the Polygon ecosystem and connected to Ethereum through the Agglayer, it is a chain where nearly all activity is DeFi activity: vault rebalances, oracle updates, position management and the bots that arbitrage between them. It is fully EVM compatible, so ethers.js, viem, Foundry and Hardhat work unchanged. The workload profile is intense, strategies and keepers polling state on every one-second block, exactly the pattern where shared public endpoints start throttling.

Common Use Cases on Katana

Yield strategies and vault keepers Automated strategies rebalance against pool and lending state continuously. Their backends poll eth_call on every block to keep positions optimal, sustained load that needs consistent latency.

Liquidation bots Concentrated lending markets mean concentrated liquidation opportunities. Liquidation bots watch health factors at high frequency and compete on reaction time when prices move.

Arbitrage between venues Arbitrage across Katana’s core venues and against other chains is a latency game. MEV-sensitive workloads need a provider whose p99 stays flat under concurrent request load.

Indexers and analytics TVL dashboards and strategy analytics backfill history and follow the chain head. An eth_getLogs pipeline over one-second blocks runs around the clock; fixed per-method pricing keeps it predictable.

Built for teams that ship on Katana.

Built for concentrated DeFi

On a chain designed around a handful of core protocols, everyone reads the same contracts. A dedicated endpoint keeps your eth_call latency flat when a market move sends every strategy and keeper to the same state at the same moment.

Debug methods included

BoltRPC serves debug_* methods on Katana, so you can trace a reverting vault interaction or inspect execution without running your own node. Method availability is measured live against our own infrastructure.

EVM compatibility, zero migration friction

Katana is fully EVM compatible. Contracts, scripts and infrastructure written for Ethereum or Polygon work unchanged: switch the RPC URL, set Chain ID 747474, and you are live.

WebSocket streaming included

Subscribe to new blocks and contract events over WebSocket at no extra charge. Keepers and monitoring react to events as they land instead of polling for them.

The Polygon ecosystem from one provider

BoltRPC serves Katana alongside Polygon PoS, Ethereum and 20+ other networks behind one dashboard and one key pattern. Strategies that span the Agglayer talk to every chain through the same provider.

Full JSON-RPC coverage.

Every standard Katana method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD5

eth_calleth_getLogseth_sendRawTransactioneth_getTransactionReceiptdebug_traceTransaction

Katana, explained.

Common questions about connecting to Katana over BoltRPC.

Ask a question →Read the docs

: The Katana Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/katana. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 747474.
: Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC Katana, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/katana, Chain ID: 747474, Currency Symbol: ETH.
: Yes. Katana is fully EVM compatible. Solidity contracts deploy without modification, and standard Ethereum tooling, ethers.js, viem, Foundry, Hardhat, MetaMask, works out of the box. Only the RPC URL and Chain ID (747474) change.
: Katana concentrates liquidity in a curated set of core protocols instead of hosting hundreds of competing deployments, and it routes bridged assets into productive yield by design. The goal is deeper liquidity and better rates in fewer venues.
: Katana uses ETH for gas. Transaction fees are paid in ETH like on Ethereum and most of its Layer 2 ecosystem.
: Public Katana endpoints are shared infrastructure serving many applications simultaneously. Under load they rate-limit requests, return stale block data, and drop WebSocket connections. Production applications need a dedicated provider with consistent response times.
: Yes. BoltRPC provides WebSocket endpoints for Katana at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/katana. Use WebSocket when you need real-time event streaming: new blocks, pending transactions, contract event logs.

Ship on Katana this week.

An API key in under 60 seconds, Katana plus 34 other chains, and a team that answers when you write.

Start free trial View pricing