What is the Starknet RPC URL?

The Starknet Mainnet RPC URL with BoltRPC is https://eu.endpoints.matrixed.link/rpc/starknet?auth=YOUR_API_KEY. Replace YOUR_API_KEY with your API key from trial.boltrpc.io. The network identifier is SN_MAIN.

Is Starknet EVM-compatible?

No. Starknet runs on the Cairo VM, not the EVM. Smart contracts are written in Cairo, not Solidity. The RPC uses starknet_* methods instead of eth_* methods. You need starknet.js or starknet-rs to interact with Starknet.

What is the difference between Starknet and zkSync Era?

Both are ZK rollups settling to Ethereum. Starknet uses ZK-STARK proofs and runs on the Cairo VM - it is not EVM-compatible. zkSync Era uses ZK-SNARK proofs and is EVM-compatible with native account abstraction.

Cairo is Starknet's native smart contract language, designed to be provable by ZK-STARK proofs. Cairo is not Solidity-compatible. Developers building on Starknet write smart contracts in Cairo.

What Starknet RPC methods does BoltRPC support?

BoltRPC supports the full Starknet JSON-RPC specification including starknet_blockNumber, starknet_getBlockWithTxs, starknet_call, starknet_estimateFee, starknet_addInvokeTransaction, starknet_getEvents, and all other standard Starknet methods.

Does BoltRPC support WebSocket for Starknet?

Yes. BoltRPC provides WebSocket endpoints for Starknet at wss://eu.endpoints.matrixed.link/ws/starknet?auth=YOUR_API_KEY.

What is the difference between STRK and ETH on Starknet?

Starknet uses two tokens: ETH for gas fees (bridged from Ethereum) and STRK, Starknet's native token. STRK was introduced as part of Starknet's decentralization roadmap. Most existing transactions use ETH for fees, but STRK fee payment is increasingly supported.

Starknet RPC Endpoint | Flat-Rate Pricing

Quick connect

Your endpoint, ready in one line.

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

HTTPS

https://eu.endpoints.matrixed.link/rpc/starknet?auth=YOUR_API_KEY

WebSocket

wss://eu.endpoints.matrixed.link/ws/starknet?auth=YOUR_API_KEY

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

Connect

Pick your stack.

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

import { RpcProvider } from "starknet";

const provider = new RpcProvider({
  nodeUrl: "https://eu.endpoints.matrixed.link/rpc/starknet?auth=YOUR_API_KEY",
});

const block = await provider.getBlockNumber();

import { RpcProvider, Contract } from "starknet";

const provider = new RpcProvider({
  nodeUrl: "https://eu.endpoints.matrixed.link/rpc/starknet?auth=YOUR_API_KEY",
});

const contract = new Contract(abi, contractAddress, provider);
const result = await contract.balanceOf(address);

curl https://eu.endpoints.matrixed.link/rpc/starknet?auth=YOUR_API_KEY \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"starknet_blockNumber","params":[],"id":1}'

Why BoltRPC

Built for teams that ship on Starknet.

Production-grade infrastructure for Cairo VM applications

Starknet's ecosystem is past early adopter stage. Production protocols running on Starknet need a provider that treats Starknet as a first-class supported chain, not an afterthought. BoltRPC provides dedicated Starknet infrastructure with the same reliability standards as its EVM chains.

ZK-STARK proof workloads demand more from infrastructure

Starknet's proving pipeline puts heavier demands on node infrastructure than standard EVM chains. ZK-STARK proof generation runs alongside standard JSON-RPC requests. BoltRPC's Starknet nodes are sized for production RPC volume alongside proof processing.

Full Starknet JSON-RPC specification

BoltRPC supports the full Starknet JSON-RPC specification including starknet_getBlock, starknet_call, starknet_addInvokeTransaction, and all standard methods. No partial implementation or missing endpoints.

Cairo ecosystem growth demands reliable access

Starknet's native smart contract language (Cairo) has a growing developer ecosystem. DeFi, NFT, and gaming protocols on Starknet all require reliable RPC access. As the ecosystem grows, provider reliability becomes more critical.

Flat-rate pricing for Starknet-native call patterns

Starknet's starknet_call and starknet_estimateFee are the workhorse methods for Cairo contract interaction. Flat pricing means your call patterns do not create billing surprises as your application scales.

WebSocket for real-time Starknet monitoring

Subscribe to Starknet events and new blocks via WebSocket. Essential for applications that need to react to contract events and proof submissions in real time.

FAQ

Starknet, explained.

Common questions about connecting to Starknet over BoltRPC.

Ask a question Read the docs

: The Starknet Mainnet RPC URL with BoltRPC is `https://eu.endpoints.matrixed.link/rpc/starknet?auth=YOUR_API_KEY`. Replace `YOUR_API_KEY` with your API key from [trial.boltrpc.io](https://trial.boltrpc.io). The network identifier is SN_MAIN.
: No. Starknet is not EVM-compatible. It runs on the Cairo VM (CairoVM), a completely different execution environment from the Ethereum Virtual Machine. Smart contracts on Starknet are written in Cairo, not Solidity. The RPC specification also differs, Starknet uses `starknet_*` methods instead of `eth_*` methods. You need starknet.js or starknet-rs to interact with Starknet, not ethers.js or viem.
: Both are ZK rollups settling to Ethereum, but they use different proof systems. Starknet uses ZK-STARK proofs and runs on the Cairo VM, it is not EVM-compatible. zkSync Era uses ZK-SNARK proofs and is EVM-compatible with native account abstraction. Starknet requires Cairo smart contracts; zkSync Era accepts Solidity. BoltRPC supports both [Starknet](/networks/starknet) and [zkSync Era](/networks/zksync).
: Cairo is Starknet's native smart contract programming language. It is designed to be provable, Cairo programs can be efficiently verified by ZK-STARK proofs. Cairo is not Solidity-compatible. Developers building on Starknet write smart contracts in Cairo rather than porting existing Solidity contracts.
: BoltRPC supports the full Starknet JSON-RPC specification including: `starknet_blockNumber`, `starknet_getBlockWithTxs`, `starknet_getTransactionByHash`, `starknet_getTransactionReceipt`, `starknet_call`, `starknet_estimateFee`, `starknet_addInvokeTransaction`, `starknet_addDeclareTransaction`, `starknet_getEvents`, and all other standard Starknet methods.
: Yes. BoltRPC provides WebSocket endpoints for Starknet at `wss://eu.endpoints.matrixed.link/ws/starknet?auth=YOUR_API_KEY`. Use WebSocket for real-time Starknet event subscriptions and block monitoring.
: Starknet uses two tokens: ETH for gas fees (bridged from Ethereum) and STRK, Starknet's native token that can also be used for fees. STRK was introduced as part of Starknet's decentralization roadmap. Most existing Starknet transactions use ETH for fees, but STRK fee payment is increasingly supported by wallets and protocols.

Starknet