RPCsUpdated

Viction RPC endpoints: free public URLs by latency

HTTP round-trip latency for eth_getBlockByNumber against every available public Viction node, audited every 60 seconds from 3 regions.

TL;DR. As of , dRPC has the lowest median latency of the 3 free public Viction RPC endpoints measured, 70 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/viction-rpc. Chain ID 88. 3 public endpoints, no key: viction.drpc.org, rpc.viction.xyz, rpc2.viction.xyz. Full URLs with their 24h median are listed below.

Companion page

Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →

Viction (formerly TomoChain) is a proof-of-stake-voting EVM L1 blockchain (chain ID 88) with 2-second block times, targeting low fees and high throughput for DeFi and NFTs. It exposes a standard Ethereum JSON-RPC interface. Public EVM endpoints are available without an API key from Viction Official, Viction RPC2 and dRPC. Every provider was live-verified with consecutive eth_getBlockByNumber probes at launch.

Methodology

Viction: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. dRPC leads at 70 ms; the chain-official endpoint measures 154 ms. We measure the round-trip latency of a single eth_getBlockByNumber ("latest", false) call against every available public Viction node that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a standard EVM staleness gap. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Viction-scoped answer with per-region breakdowns as a first-class dimension.

  • Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus avg(quantile_over_time(...)); per-region breakdowns are first-class on this page via the region tabs.
  • Payload: {"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest",false]}. Plain HTTP POST. Standard Ethereum JSON-RPC 2.0.
  • Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Viction-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to chain=viction. Provider coverage today: 3 endpoints.

Results: 3 free public Viction RPC endpoints ranked by p50 latency (24h, 3 regions)

Viction RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1dRPCdRPC decentralised multi-chain RPC, public Viction endpoint, no key required70 ms107 ms221 ms99.70% (n=4320)
2Viction OfficialViction official public RPC, keyless154 ms187 ms450 ms99.88% (n=4319)
3Viction RPC2Viction secondary public RPC (rpc2.viction.xyz), keyless174 ms465 ms574 ms100.00% (n=4320)

Public Viction RPC endpoints measured

Chain ID 88, currency VIC. The 3 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.

Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.

Frequently asked

Which Viction RPC endpoints work without an API key?

3 endpoints are probed on this chain: Viction Official (rpc.viction.xyz), Viction RPC2 (rpc2.viction.xyz) and dRPC (viction.drpc.org). Every listed endpoint was live-verified with an eth_getBlockByNumber call returning a parsable block number before inclusion.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities