Dedicated B3 RPC Node & B3 RPC Endpoint | RedSwitches
// dedicated b3 rpc node

Private B3 RPC Endpoints on a Dedicated Node

A private B3 RPC endpoint on single-tenant NVMe bare metal. Full or archive OP Stack nodes serving HTTPS and WebSocket, with zero rate limits and no compute units.

Get a QuoteStart Live Chat
  • Private Endpoint, Zero Rate Limits
  • No Compute Units, Unlimited Requests
  • Full & Archive Builds
  • OP Stack On Base, Your Config
  • HTTPS & WebSocket Endpoints
  • 20+ Global Tier III Locations
deploy.shlive

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

allocating single-tenant bare metal

restoring op-geth snapshot

connecting base parent-chain rpc

starting op-node rollup client

attaching DDoS shield + IP allowlist

private endpoint live · https + wss

region Frankfurt · op-geth + op-node · ~1-2s blocks

  • UnlimitedRequests
  • ZeroRate Limits
  • 100%Isolation
// why redswitches

Why Teams Run B3 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. op-geth and op-node config, snapshot strategy, and the Base parent-chain dependency, handled by people who run OP Stack 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, ETH 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 B3 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

B3 Full Node

For games, wallets, bots & backend APIs

CPU
8–16 high-clock cores
RAM
32–64 GB
Storage
1–2 TB NVMe (grows with state)
Network
10 Gbps uplink, metered or unmetered
Stack
op-geth + op-node + a Base parent-chain RPC
Best for
  • Game backends, claims, and consumer-app reads
  • HTTP and WebSocket subscriptions
  • Needs a Base parent-chain RPC (bring or host with us)
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.

Inquiring about: B3 · Full Node

Replies in ~5 minA RedSwitches Web3 engineer specs your private endpoint

No compute units, no rate limits. From $199/mo, flat.

Prefer to talk it through first? Start Live Chat

// why dedicated

Stop Fighting For Bandwidth On Shared B3 RPC

Shared B3 RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated B3 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 B3 calls the moment traffic spikesZero rate limits, your B3 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 B3 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 B3 endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull B3 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 B3 client and tuning you choose
// network details

B3 Node Specifications

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

Chain Parameters

Networks
B3, B3 Sepolia
Chain IDs
B3 8333 · B3 Sepolia 1993
Native token
ETH
Stack
OP Stack rollup, settles on Base (Base settles to Ethereum L1)
Block time
~1 to 2 seconds
Transports
HTTPS and WebSocket
Archive
Full historical state, no pruning
Dependency
Requires a Base parent-chain RPC endpoint
Explorer
explorer.b3.fun (Blockscout)

Supported Clients

Execution client
  • op-geth
Rollup node
  • op-node

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 B3 Nodes

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

Live Game Operations

When a game writes match results, inventory changes, or reward claims in bursts, shared RPC turns unpredictable. A dedicated B3 RPC node gives your backend steadier reads and sends during the moments players notice most.

Appchain Launch Journeys

B3 promotes purpose-built appchains with a unified cross-chain experience. A dedicated node fits teams moving users through wallet setup, bridging, minting, and gameplay flows without leaning on public infrastructure during high-friction launch stages.

Drop Window Traffic

Listings, claims, and limited releases compress demand into short windows. A private B3 RPC endpoint helps marketplaces keep ownership checks, stock visibility, and checkout logic moving when readers turn into buyers all at once.

Reward Claim Engines

Loyalty systems, quest payouts, and seasonal rewards create repetitive claim traffic that punishes shared endpoints. A dedicated B3 RPC node fits products needing claim validation, balance checks, and payout status to stay responsive under repeat demand.

Historical State Analysis

Some provider setups expose no archive and only 128 blocks of history. Dedicated infrastructure makes sense when your team needs older state, support audits, analytics backfills, or investigation beyond the latest chain view.

Region-Aware Routing

Consumer apps rarely serve one geography. Dedicated B3 RPC placement closer to players, collectors, or backend systems trims avoidable latency and gives teams more control over how regional traffic splits as the product grows.

// how it works

From B3 To Private Endpoint In 3 Steps

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

  1. 01

    Pick Your B3 Node

    Choose full or archive, and bring or host the Base parent-chain RPC your op-node depends on. Pick the region closest to your players.

  2. 02

    We Provision Bare Metal

    Your single-tenant op-geth and op-node deploys on dedicated NVMe, bootstrapped from a current snapshot, so you skip the long replay.

  3. 03

    Get Your Private Endpoint

    Receive a dedicated HTTPS and WSS RPC endpoint 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 B3 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 the B3 sequencer 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.

// customer reviews

Trusted To Run Production Nodes

Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.

  • 4.8/525Gbps Bare Metal
    Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
    Felix MartinsenDenmark
  • 5.0/5VPN Operations
    Network has been rock solid. They’ve got Tier 1 carriers like Arelion, GTT, and TATA… We just ping them on Telegram and they sort things out quickly.
    TomasNetherlands
  • 4.8/5Validators
    Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
    Peppe TerranovaSouth Korea
  • 5.0/5Full Root Access
    As a sysadmin, I care more about control than flashy dashboards. RedSwitches gives me root access, IPMI, and actual hardware specs I can configure. Good for serious users.
    Eun-Woo GimSouth Korea
  • 5.0/5Enterprise Uptime
    We were searching for a truly reliable and stable hosting provider with maximum uptime and a powerful network infrastructure to ensure the lowest possible latency. RedSwitches not only met but exceeded our expectations.
    AppsLabGermany
  • 5.0/5Cloud Exit
    RedSwitches gave us full control over our infrastructure without the vendor lock-in we kept running into with cloud hosts. Customizable builds, fast provisioning, and actual humans handling support tickets. It’s refreshing.
    Princeton OttUnited States
  • 5.0/599.99% Uptime
    My website works smoothly, thanks to their 99.99% uptime guarantee. The support team is another plus for me, as I always have been able to get help whenever I needed it in just 5 minutes on average.
  • 5.0/5ETH & BTC Nodes
    Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
    Ervin KaruGermany
  • 5.0/510Gbps RPC
    They provide what they promise, I got no throttling while running my RPC Nodes. I got server in a Amsterdam for the best price.
    Atri MukherjeeIndia
  • 5.0/5Streaming
    I am using their 10gbps streaming server for last 6 months and I have no complaints. Extremely quick live chat support and I love that they accept crypto.
    Tarun GhoshIndia
  • 5.0/5Bare Metal
    A really great hosting provider - what stands out the most is the stability of the network connection and the wide selection of bare metal servers. We’re very satisfied, and RedSwitches covers all of our needs.
    Борис ВербицкийPoland
  • 5.0/5AI Workloads
    Pros: Extremely reliable hardware, low-latency network, transparent billing… Great choice if you need raw power without cloud complexity. Works well for our dev environment and some AI workloads.
    Henry HarrisonUnited States
  • 5.0/5Switched Provider
    I have worked with OVH and Contabo in the past, but RedSwitches hit a better balance of price vs. support. Not the cheapest, but I get better performance and faster help.
    Samual SuttonUnited Kingdom
  • 5.0/5Game Servers
    Been using RedSwitches for 6 months now for my small game server biz. Uptime has been great, and I haven’t run into any hidden charges.
    Jerold PerkinsUnited States
  • 5.0/5AI Storage
    Using the storage servers to archive logs and snapshots from our AI pipeline… I also love that I could pick the datacenter closest to our team.
    Eino KoppelEstonia
  • 4.8/5Support
    Support is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
    Boniface LeandreUnited States
  • 5.0/5Instant Delivery
    They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
    Daniel StuartSri Lanka
  • 5.0/5Fast Provisioning
    A dedicated server has been installed within 30 minutes. Thirty minutes. It takes DAYS for some famous providers out there, but these guys do their work right.
    Ярослав СавенковNetherlands
  • 5.0/55+ Years
    I have been using their services for over 5+ years… Uptime: 10/10, Network: 10/10, Hardware Quality: 10/10, Customer Support: 20/10 (No, That’s Not A Typo).
  • 5.0/51 to 14 Servers
    They offer top quality hardware, excellent uptime and very responsive support… They helped us scale our business exponentially and we went from 1 server to 14 dedicated servers in less than a year.
    Sandip PanditIndia
  • 5.0/5Reliability
    Great hardware, non congested network and excellent service. Already using them for over a year and would definitely recommend Redswitches if you are looking for a reliable hosting provider.
    CandiceUnited States
  • 4.8/5Global Locations
    With servers available in numerous strategic locations, RedSwitches offers exceptional versatility and performance for our company’s diverse hosting needs. Plus, their no setup fee policy really helps keep costs down.
    Tiberiu RomanUnited States
  • 5.0/5Exam Platform
    "Your server is ready" - I read this message within 30 mins of starting the chat with their Sales Team… Excellent DELL Hardware and 100% Uptime.
    Mridul MehtaIndia
  • 5.0/5Bare Metal Cloud
    The dedicated server I got from RedSwitches has been incredibly reliable and fast. Their bare metal cloud solutions offer excellent performance, and the cloud VPS options are perfect for scaling. Highly recommended!
  • 5.0/5Zero Downtime
    I have been using their dedicated server from 9 months now. Starting from pre-sales till today I have not experienced downtime or lack of support.
    Amit BhatiaIndia
  • 5.0/524/7 Support
    First of all, all services work as expected - secondly - support is outstanding, no matter when you start the conversation with colleagues at support they have knowledge to help you out.
    LukaSlovenia
  • 5.0/5Since 2021
    We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
    Eitan WaisgerberIsrael
  • 5.0/5Easy Onboarding
    Absolutely delighted with RedSwitches! The setup was quick and free, and the fact that they accept all major payment gateways made the process seamless.
    Birk SpillumNorway
  • 5.0/5Bare Metal
    Very good experience using their bare metal servers. Their customer service is one of the finest I have experienced - always prompt at resolving troubles. Highly recommend.
// faqs

Frequently Asked Questions

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

What is a B3 RPC node?

A B3 RPC node is the server endpoint your app uses to read blockchain data, submit transactions, and listen for chain events on B3. B3 Mainnet uses chain ID 8333, the native gas token is ETH, and the official public RPC listed by B3 is https://mainnet-rpc.b3.fun. Since B3 is positioned as Base's layer 3 consumer ecosystem for games, apps, and enterprises, the node sits at the center of user actions such as reads, sends, claims, and event-driven flows.

How is a dedicated B3 RPC node different from a public B3 endpoint?

A public endpoint is shared infrastructure. It is useful for quick starts, testing, and lighter workloads. A dedicated B3 RPC node gives you single-tenant compute, private access options, stronger traffic isolation, and cleaner control over reads, writes, and WebSocket traffic. That difference matters once your product moves into production, where shared and rate-limited infrastructure can become the bottleneck. Base says its public RPCs are rate-limited and not suitable for production systems, and our dedicated RPC offer is built around that production gap.

Can I run a B3 validator node?

Not in the staking sense. B3 is a Base layer-3 rollup built on the OP Stack with a centralized sequencer, so there is no permissionless, stake-to-earn validator like Ethereum or Solana. What we provision is what apps and indexers actually need: a fast, dedicated full or archive RPC node running op-geth and op-node. If your goal is throughput, history, and private access rather than block production, a dedicated RPC node is the right build.

Do I need Base parent-chain access to run a B3 RPC node?

Yes. Like every OP Stack node, B3 derives its state from its parent chain, so your node must connect to a Base execution RPC endpoint to follow the canonical chain. If that parent-chain endpoint is slow or rate-limited, your node can fall behind, which shows up as stale reads and delayed indexing. You can bring your own Base endpoint, or run it on dedicated servers with us, ideally in the same region for tighter latency and faster catch-up.

Is B3 EVM-compatible, and will my existing Ethereum tooling work on it?

Yes. B3's docs say the network is fully EVM-compatible, and they show standard wallet setup for MetaMask, Coinbase Wallet, and Rainbow. In practice, that means most Ethereum-style tooling, contracts, and developer flows carry over much more easily than they would on a non-EVM chain. From our side, that makes a dedicated B3 RPC node a practical fit for teams already working with Ethereum-like JSON-RPC patterns and wallet flows.

Do you support both HTTP and WebSocket access for B3 RPC?

Yes. We can design B3 deployments for both request-response traffic and live event delivery when your workload needs HTTP and WebSocket access. B3 provider ecosystems commonly expose both HTTP and WSS access patterns. For production, we usually treat HTTP and WebSocket traffic as different load shapes, then size the server and routing plan around the mix you expect instead of assuming one endpoint profile fits everything.

When should I choose a full node instead of an archive build for B3?

Choose a full node when your app mostly cares about current state, recent blocks, transaction submission, and normal event handling. Choose an archive build when you need deeper historical state, older-block analysis, tracing-heavy workflows, or support investigations that go well beyond the latest view of chain data. This matters on B3 because some provider offerings expose no archive and only 128 blocks of state history, which is fine for many apps but not for every product or ops workflow. On the OP Stack side, archive planning also needs more care around snapshots and sync strategy than a standard full node.

What hardware baseline do you recommend for a production B3 full node?

For a serious production starting point, we would usually begin around 16 high-clock cores, 64 GB RAM, fast local NVMe, and a 10 Gbps uplink, then move up based on read intensity, WebSocket concurrency, history needs, and retention targets. That recommendation is more conservative than a bare-minimum setup because OP Stack style deployments are resource-heavy, and because Base's own node docs call out 8 cores, at least 16 GB RAM, and locally attached NVMe as a basic setup while its performance guide raises that toward 32 GB minimum and 64 GB recommended. We would rather size you for a stable production floor than force an early rebuild.

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

B3 Developer Resources

Official B3 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 B3 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.

Get a QuoteStart Live Chat