Changelog

What’s new

v1.6.0 — 1 August 2026

Direct crypto payments — straight to our own wallet

  • Crypto checkout no longer goes through a payment processor: plans and CU top-ups are now paid directly to NodeFlare's own wallet — you send an exact amount, we verify it on-chain on our own nodes, and your plan activates the moment the transfer confirms
  • Four assets: USDC and USDT (on Ethereum, Base, Arbitrum, Optimism or Solana, where each is natively issued), native ETH (Ethereum, Base, Arbitrum, Optimism) and native SOL — native coins quoted at the live market price when your invoice opens
  • 10-minute payment window with a live countdown; late payments keep being detected for 24 hours
  • Card payments via Stripe are unchanged

v1.5.0 — 1 July 2026

Per-method API reference, docs corrections, dashboard polish

  • New per-method API reference: every JSON-RPC method documented per chain — parameters, compute-unit cost, curl/ethers examples (browse from any chain page)
  • New per-chain landing pages and solutions pages (trading bots, indexing, wallets, DeFi)
  • WebSocket now available on all 7 chains through the gateway (previously Ethereum, Base and HyperEVM only) — format: wss://rpc.nodeflare.app/{chain}/ws/v1/{key}, with rate limiting and method guards applied
  • Dashboard: /app now redirects to the overview, paid plans get a Manage subscription button (Stripe portal — update card, download invoices, cancel), usage card shows an upgrade prompt above 80%, account page shows your profile
  • Blog now has an RSS feed and structured article metadata
  • Corrected stale compute-unit figures in older posts (current weights: rate limits)

v1.4.0 — 2 June 2026

Heavy methods on the free tier

  • eth_getLogs, eth_getFilterLogs, filter methods, trace_* and debug_* are now available on the Free plan (and all paid plans) — previously key-only on paid. They remain restricted on the public no-key endpoint
  • These heavy methods now carry higher CU weights so the monthly quota throttles abuse: eth_getLogs/eth_getFilterLogs = 75 CU, trace_*/debug_* = 100 CU, filter/proof methods = 20 CU (full table)
  • Requests are now capped at 100 calls per batch and a 256 KB body to protect upstream nodes
  • Public endpoint rate limit documented accurately: 2 req/sec · 500 req/day

v1.3.0 — 19 May 2026

Compute Units billing

  • Usage is now measured in Compute Units (CU) instead of raw request counts — heavier calls cost more quota, lighter calls cost less
  • Per-method CU weights: eth_blockNumber = 1 CU, eth_call = 5 CU, eth_getLogs = 15 CU, trace_* = 25 CU (full table)
  • Batch requests sum the CU of every call in the batch
  • Extra CU top-up (1M for €5) now deducts at the correct per-method rate instead of a flat 1 per request
  • Referral reward updated to 500,000 CU
  • Usage tracking is now real-time accurate — counts reflect all requests including the last 30 seconds
  • Dashboard usage card updated to show CU consumed with per-chain breakdown

v1.2.0 — 18 May 2026

5 regions, 17 nodes, WebSocket endpoints

  • Added London region: Base, BNB, Avalanche, Arbitrum nodes
  • Added Falkenstein region: BNB, Arbitrum, Optimism nodes
  • Added Los Angeles region: Base, Avalanche nodes
  • Added Avalanche C-Chain (chain ID 43114) — 7th supported chain
  • WebSocket endpoints now live for all chains — see individual chain docs
  • Health monitoring tracks all 17 nodes across 5 regions
  • Geo-aware routing sends requests to the nearest region automatically

v1.1.0 — 16 May 2026

Singapore region + geo routing

  • Added Singapore region: Base, BNB, Arbitrum nodes
  • Geo-aware routing via Cloudflare colo detection (APAC, AMER, London, EU)
  • Multi-node failover: automatic fallback to next healthy node on 5xx or timeout
  • Per-minute health checks across all nodes with 30-day uptime history

v1.0.0 — 15 May 2026

Initial launch

  • JSON-RPC proxy for 6 EVM chains: Ethereum, Base, BNB, Arbitrum, Optimism, HyperLiquid
  • Free tier: 100K CU/month
  • Paid plans: Starter (5M CU/mo) and Pro (50M CU/mo)
  • Stripe and crypto (NOWPayments) billing
  • Per-chain usage tracking in dashboard
  • Clerk authentication
  • GDPR-compliant privacy policy and Terms of Service