Unlimited Node
Run Ink indexers and application backends with unlimited requests within your selected RPS tier. Keep monthly RPC costs predictable as request volume grows.
Build trading and lending apps on Ink, the Ethereum layer 2 built by Kraken, with reliable HTTPS and WebSocket RPC.

Connect your application to Ink Mainnet over HTTPS and WebSocket. Read contract state, follow events, and submit signed transactions with familiar Ethereum tools.
Build Ink applications with archive state, execution traces, and predictable RPC capacity.
Run Ink indexers and application backends with unlimited requests within your selected RPS tier. Keep monthly RPC costs predictable as request volume grows.
Query historical contract state and backfill event logs for Ink indexers, accounting, and DeFi analytics.
Inspect Ink transaction execution, diagnose reverted calls, and investigate internal contract activity with debug APIs.
Read pool state, simulate calls, and submit signed swaps. Connect trading interfaces to Ink with ethers.js or viem.
Explore Ink toolingRead collateral, debt, and market state from lending contracts. Follow protocol events to keep position dashboards current.
Get an Ink endpointBackfill logs with eth_getLogs and subscribe to new events over WebSocket. Use bounded block ranges for your historical indexer.
Read the Ink endpoint guideCombine Kraken’s exchange APIs with Chainstack Ink RPC to compare exchange prices with onchain liquidity, monitor wallet funding, and track swaps.
Explore Ink toolingInspect transactions with op-reth debug and trace APIs on paid plans. Diagnose reverted calls and follow internal execution.
Explore Ink debug APIsChoose Ink mainnet and an available node configuration to estimate monthly infrastructure costs.
Choose an available Ink network and node configuration to estimate monthly infrastructure costs.
Customer stories from teams using Chainstack across supported networks.
Follow new blocks and contract logs over WebSocket, then backfill event history over HTTPS. Build trading, lending, and wallet workflows around confirmed receipts and the state your application needs.
Get an Ink endpointRead token-transfer events from the latest Ink block with eth_getLogs.
https://ink-mainnet.core.chainstack.com/YOUR_ENDPOINT_IDwss://ink-mainnet.core.chainstack.com/YOUR_ENDPOINT_IDCreate an Ink node. Copy your authenticated HTTPS URL from Access and credentials and replace YOUR_ENDPOINT_ID in the example.
curl --request POST \
--url https://ink-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID \
--header 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "eth_getLogs",
"params": [
{
"fromBlock": "latest",
"toBlock": "latest",
"topics": [
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"
]
}
]
}'The result is an array of matching logs. Paginate historical backfills in bounded block ranges and filter by the contract addresses your application follows.
Start with free Ink RPC. Scale your application with paid plans, higher throughput, and dedicated infrastructure.
Includes:
All Developer features, plus:
Add-ons and Dedicated Node infrastructure are billed separately.
Explore Ink RPC, application development, and infrastructure guides.

Connect your wallet, application, or indexer to Ink.
Read article
Review endpoint features, pricing, and production tradeoffs.
Read article
Explore Kraken’s OP Stack L2 and its developer workflows.
Read article
Explore archive data, tracing, and managed node options.
Read articleConnect to Ink Mainnet at https://ink-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID. Copy the authenticated URL from Access and credentials. Mainnet uses chain ID 57073 and ETH for gas. Chainstack currently serves Ink Mainnet only. See the Ink tooling guide.
Use eth_getBalance for ETH balances, eth_call for contract reads, eth_getLogs for event history, and eth_sendRawTransaction for signed transactions. Connect over WebSocket for supported new-block and log subscriptions. Paginate event backfills and account for both L2 execution fees and L1 data fees. A pending tag is not a public mempool subscription. See Ink’s RPC behavior.