// dedicated viction rpc node

Private Viction RPC Endpoints on a Dedicated Node

A private Viction RPC endpoint on single-tenant NVMe bare metal. Full, archive, or validator nodes serving standard Ethereum JSON-RPC, with zero rate limits and no compute units.

Get a Quote Start Live Chat

Private Endpoint, Zero Rate Limits
No Compute Units, Unlimited Requests
Full, Archive & Validator Builds
EVM-Compatible Ethereum JSON-RPC (eth_*)
~2s Blocks On Fast Local NVMe
20+ Global Tier III Locations

deploy.shlive

$ rs deploy viction --type full --region fra

allocating single-tenant bare metal

syncing tomochain (tomo) client

serving ethereum json-rpc (eth_*)

exposing http 8545 + ws 8546

attaching DDoS shield + IP allowlist

private endpoint live · https + wss

region Frankfurt · PoSV consensus · ~2s blocks

UnlimitedRequests
ZeroRate Limits
100%Isolation

// why redswitches

Why Teams Run Viction Nodes With RedSwitches

A single-tenant node with people behind it: unlimited throughput, a named account manager, direct engineering access, and billing built for Web3 teams.

Unlimited RPS & Responses

One node, unlimited requests and responses. No compute units, no rate caps, no overage bills. A flat monthly price, run as hard as the hardware allows.

Dedicated Account Manager

A named account manager who knows your setup, not a ticket queue. One contact for provisioning, scaling, and anything urgent.

Direct Engineering Access

Talk to the engineers who run the metal. tomochain (tomo) client config, RPC namespace tuning, and PoSV masternode setup, handled by people who run Viction nodes daily.

20+ Global Data Centers

Place your node beside your users across 20+ Tier III locations. Multi-region for redundancy, split read and write endpoints.

Pay In Crypto

Settle in crypto or fiat, VIC included. Flexible billing for Web3 teams, with the same predictable flat monthly price either way.

Tailored Load Balancing

Custom load balancing, failover, and split read/write topology, designed and tuned for your traffic by our engineers.

// request your endpoint

Configure Your Viction Node

Pick a node type, tell us your workload, and an engineer sizes and quotes it. One flat monthly price, no compute units, no overages.

1 Dedicated Node = Unlimited RequestsNo Compute Units$0 Overages, Guaranteed

Viction Full Node

For dApps, wallets, bots & backend APIs

CPU: 8–16 high-clock cores
RAM: 16–32 GB
Storage: 1–2 TB local NVMe (grows with chain state)
Network: 1 Gbps+ on a 10/25 Gbps port
Clients: tomochain (tomo) · Ethereum JSON-RPC compatible

Best for

Reads, logs, and contract calls on Viction
HTTP RPC on 8545 and WebSocket on 8546
Recent-state queries for production apps

Included with every node

Unlimited RPS, no rate limits
HTTPS & WebSocket (WSS)
99.99% uptime SLA
Multi-region endpoints
Private networking + IP allowlisting
24/7 Web3 engineering support

From$199/moflat, no compute units

Final price is sized to the node specs your chain needs (full vs archive, storage, region), and typically lands 30-40% below comparable RPC providers.

Node specs above are based on the official Viction documentation.

View official Viction node docs →

// why dedicated

Stop Fighting For Bandwidth On Shared Viction RPC

Shared Viction RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Viction node is your own private backbone: flat-priced, uncapped, and yours alone.

CapabilityShared RPC PoolRedSwitches Dedicated

Request limitsHard rate caps and compute-unit quotas throttle your Viction calls the moment traffic spikesZero rate limits, your Viction node serves unlimited requests up to what the hardware can push

ResourcesA noisy-neighbor pool where another tenant's mint or airdrop steals the throughput you paid for100% single-tenant CPU, RAM, and NVMe, reserved for your Viction workload alone

BillingPer-compute-unit metering with surprise overage bills at the end of the monthOne flat monthly price for the whole node, $0 overages and no usage math

NetworkShared, throttled bandwidth you can neither see nor controlA dedicated 10 / 25 Gbps port, metered or unmetered, that is yours alone

PrivacyA public, pooled endpoint with a wide, shared attack surfaceA private Viction endpoint behind included DDoS protection and IP allowlisting

History & specsLimited history and fixed plans you cannot resize as you growFull Viction archive with custom RAM and disk, sized to your query depth

ControlNo server access, the provider picks the client, version, and configFull root, KVM, and IPMI, run the Viction client and tuning you choose

// network details

Viction Node Specifications

The chain IDs, clients, transports, and JSON-RPC namespaces your dedicated Viction node ships with. Built to a standard so your existing tooling connects with no changes.

Chain Parameters

Networks: Viction Mainnet, Viction Testnet
Chain IDs: Mainnet 88 (0x58) · Testnet 89
Native token: VIC (formerly TOMO)
Consensus: Proof of Stake Voting (PoSV), 150 masternodes
Block time: ~2 seconds
VM / Execution: EVM-compatible (Ethereum JSON-RPC)
RPC ports: HTTP 8545 · WebSocket 8546
Gas model: Zero-gas / gas-sponsored transactions (VRC25)
Archive: Full historical state
Explorer: vicscan.xyz

Supported Clients

Node software

tomochain (tomo) — go-ethereum fork

JSON-RPC Namespaces

eth_
net_
web3_
debug_
txpool_

You control which namespaces are exposed. Enable debug and trace on archive builds, keep the rest private behind IP allowlisting.

// use cases

What Teams Build On Viction Nodes

Where a private, uncapped endpoint beats a shared RPC pool.

Zero-Gas dApp Backends

Power VRC25 zero-gas and gas-sponsored apps with a private endpoint. Dedicated CPU and NVMe keep reads and contract calls fast as gasless transaction volume climbs.

NFT & VRC725 Indexing

Track Viction NFT and VRC725 activity without public limits. Isolated I/O keeps mint status, metadata reads, and event indexing consistent through demand spikes.

Wallet & Exchange Integration

Serve balances, deposits, and confirmations from a node that is yours alone. Dedicated resources cut the timeouts that cause missed deposits and delayed crediting.

Masternode Operations

Run a PoSV masternode candidate on hardware you control. Steady uptime, full root, KVM, and IPMI for fast recovery, with your validator keys held by you.

Indexer Backfill Runs

Backfill receipts and event logs without slowing production. NVMe capacity and RAM keep long-range historical ingestion consistent across days at production speed.

Multi-Region Read Layer

Deploy Viction nodes close to users across regions. A primary endpoint plus regional readers smooths global read traffic without routing everything to one location.

// how it works

From Viction To Private Endpoint In 3 Steps

Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.

01
Pick Your Viction Node
Choose full, archive, or masternode. Viction is EVM-compatible and serves standard Ethereum JSON-RPC, so tell us your tier and the region closest to your users.
02
We Provision Bare Metal
Your single-tenant tomochain (tomo) node deploys on fast local NVMe and is snapshot-synced, so you skip the long cold sync from genesis.
03
Get Your Private Endpoint
Receive a dedicated Ethereum JSON-RPC endpoint (HTTP and WebSocket) with unlimited requests and zero rate limits, private behind IP allowlisting and DDoS protection.

// latency & locations

Put Your Node Where Milliseconds Are Won

RPC latency is mostly a function of distance. A dedicated node lets you choose the exact region, so you sit next to the traffic that matters instead of fighting for routing on a shared, far-away endpoint.

Place It Where Your Users Are

Deploy across 20+ Tier III locations in the US, EU, Asia, and Australia. Put your Viction node in the region your traffic actually comes from, not wherever a shared pool happens to route you.

Cut The Round Trips

RPC latency is mostly physical distance. Running in the same region as your users and the Viction network's peers shaves the round-trips a far-away, shared endpoint can never give back, which is what high-frequency reads and transaction submission live or die on.

Multi-Region By Design

Run a primary node plus regional read replicas for fast reads everywhere and built-in redundancy. Split public read endpoints from private admin, debug, and trace endpoints.

Need a node within a target latency budget of a specific region or venue? Tell us the endpoint and we'll recommend the closest facility.

// supported chains

One Backbone For Every Major Chain

Run validators, RPC, and archive nodes across the chains your stack depends on, all on the same dedicated bare metal, with the same isolation, speed, and control.

Read all RedSwitches reviews, or see them on Google, HostAdvice, Cryptwerk and Trustpilot.

// faqs

Frequently Asked Questions

Chain IDs, clients, archive data, getLogs limits, and why dedicated beats compute-unit billing.

What is a Viction RPC node, and what does it do?

A Viction RPC node is a server running the tomochain (tomo) client that exposes the Ethereum JSON-RPC API your app uses to read on-chain data and broadcast transactions. Teams rely on a dedicated Viction node to serve dApps, wallets, indexers, and dashboards with stable, predictable access.

Is Viction EVM-compatible, and which RPC methods does it support?

Yes. Viction is an EVM-compatible chain, so it serves standard Ethereum JSON-RPC methods (eth_*, net_*, web3_*) and works with familiar tooling like ethers.js, web3.js, Hardhat, and Foundry. A dedicated node exposes HTTP RPC on 8545 and WebSocket on 8546.

Is Viction the same as TomoChain?

Yes. Viction is the rebrand of TomoChain, completed in November 2023, with the native token renamed from TOMO to VIC. The node software still lives in the BuildOnViction (tomochain) repositories, and the chain keeps EVM compatibility and the Proof of Stake Voting (PoSV) consensus.

How does Viction consensus and zero-gas work?

Viction secures the network with Proof of Stake Voting (PoSV), where 150 masternodes create and sign blocks using double validation and randomization for fast, fork-resistant finality. Viction also supports zero-gas and gas-sponsored transactions via the VRC25 standard, so apps can cover fees for their users.

Full node vs archive node: which one do I need?

Choose a full node when you mainly need the latest state, receipts, and recent logs for a dApp or wallet backend. Choose an archive node when you need deep historical state for analytics, explorers, audits, or long-range backfills. A dedicated setup lets you pick the right tier without shared limits.

Why choose a dedicated Viction node over shared RPC?

Shared RPC endpoints throttle, vary in latency, and change policies without warning. A dedicated Viction node runs on single-tenant CPU, RAM, and NVMe, so your throughput and response times depend on your hardware headroom, not other tenants or shared compute-unit quotas.

Do you charge per request or per compute unit?

No. Unlike shared RPC providers that bill per "compute unit" and throttle you past a quota, a dedicated node is a flat monthly price with unlimited requests and zero overages. One node equals all the throughput your hardware can serve. That makes budgeting predictable and removes the surprise bills that come with usage-based RPC pricing.

How is this different from a shared RPC endpoint?

Shared RPC pools serve thousands of customers from pooled infrastructure, so you inherit rate limits, noisy-neighbor latency, and compute-unit billing. A RedSwitches node runs on single-tenant bare metal that is yours alone: reserved CPU, RAM, and NVMe, a dedicated 10/25 Gbps port, and a private endpoint you control. Performance tracks your hardware, not another tenant's traffic.

Do I have to sync the node myself, or wait days for it?

No. We provision from current snapshots so your node is live in hours rather than syncing from genesis for days. You can run it yourself with full root access, or choose our fully managed option where our engineers handle the sync, updates, and monitoring. Either way you receive a working private endpoint, not an empty server.

Can I deploy close to a specific region or sequencer?

Yes. With 20+ Tier III locations across the US, EU, Asia, and Australia you can place your node in the same region as your users or a chain's sequencer to cut round-trip latency. Tell us your target region and we will recommend the closest facility. You can also run multi-region nodes for redundancy and split read and write endpoints.

// developer resources

Viction Developer Resources

Official Viction resources for builders running a node: docs, explorers, source, network status, and faucets. Every link points at the first-party source, not a wrapper.

// launch your node

Launch Your Private Viction Node

From $199/mo flat, sized to your chain's node specs and typically 30-40% below other providers. Snapshot-ready provisioning, zero setup fees, 24/7 Web3 engineers, no compute units, no rate limits.