Dedicated Lens RPC Node & Lens RPC Endpoint | RedSwitches
// dedicated lens rpc node

Private Lens RPC Endpoints on a Dedicated Node

A private Lens RPC endpoint on single-tenant NVMe bare metal. Full or archive External Nodes serving standard eth_ plus zks_ methods, 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 External Node Builds
  • Standard eth_ Plus zks_ Methods
  • HTTP & WebSocket RPC Ready
  • 20+ Global Tier III Locations
deploy.shlive

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

allocating single-tenant bare metal

restoring zksync external node snapshot

connecting ethereum l1 rpc

syncing lens external node

attaching DDoS shield + IP allowlist

private endpoint live · http 3060 + wss 3061

region Frankfurt · zksync external node · eth_ + zks_

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

Why Teams Run Lens 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. ZKsync External Node config, the Ethereum L1 dependency, snapshot strategy, and zks_ method tuning, handled by people who run Lens 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, GHO 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 Lens 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

Lens Full Node

For dApps, wallets, bots & indexers

CPU
8–16 modern cores
RAM
32–64 GB
Storage
~1 TB+ NVMe (700+ GB baseline, grows)
Network
100 Mbps+ on a 10/25 Gbps port (1 Gbps+ recommended)
Stack
ZKsync External Node + an Ethereum L1 RPC
Best for
  • Current-state reads, writes & contract calls
  • HTTP (3060) and WebSocket (3061) subscriptions
  • Needs an Ethereum L1 endpoint (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.

Node specs above are based on the official Lens documentation.

View official Lens node docs →

Inquiring about: Lens · 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 Lens RPC

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

Lens Node Specifications

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

Chain Parameters

Networks
Mainnet, Lens Testnet
Chain IDs
Mainnet 232 · Testnet 37111
Native token
GHO (Aave stablecoin, gas)
Stack
Matter Labs ZK Stack, ZK Validium with Avail DA, settles to Ethereum L1
VM
EVM-compatible (zkEVM)
Transports
HTTP JSON-RPC (3060) and WebSocket (3061)
Archive
Full rollup history via Postgres dump, pruning disabled
Dependency
Requires an Ethereum L1 RPC endpoint
Explorer
explorer.lens.xyz

Supported Clients

Node software
  • ZKsync External Node (matterlabs/external-node)

JSON-RPC Namespaces

  • eth_
  • net_
  • web3_
  • debug_
  • zks_

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

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

Social Feed Engines

Power apps that constantly pull Accounts, Usernames, Graphs, Feeds, and Groups. A dedicated Lens RPC node keeps reads, writes, and background jobs moving cleanly for busy social products.

Live Notification Flows

Support instant alerts for account events, feed actions, and group activity. This suits products that depend on fresh onchain activity reaching users quickly, not minutes later when delays hurt engagement.

Embedded Wallet Journeys

Run wallet-linked flows where users sign in, check balances, view profiles, and submit actions without friction. This fits teams that want Lens experiences to feel smooth inside consumer apps.

Content Automation Tools

Operate scheduled publishing, campaign execution, moderation, repost logic, and account-level automation at scale. This works best for products that trigger repeat activity all day behind a private Lens endpoint.

Creator Insight Dashboards

Track creator growth, audience actions, collection activity, and post-level engagement through structured chain data. This fits dashboards that turn Lens activity into decisions for creators and growth teams.

Paid Access Products

Build paid communities, gated content, collectible actions, and monetized journeys. A dedicated Lens node matters here because checkout-like moments need accurate state and dependable submission.

// how it works

From Lens 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 Lens Node

    Choose full or archive, and bring or host the Ethereum L1 RPC your External Node depends on. Pick the region closest to your users.

  2. 02

    We Provision Bare Metal

    Your single-tenant ZKsync External 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 HTTP and WebSocket 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 Lens 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 Lens 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 Dedicated Lens RPC Node?

A Dedicated Lens RPC Node is a private Lens Chain node that runs on single-tenant infrastructure reserved for your workloads. We use it to serve your app's reads, writes, WebSocket subscriptions, background jobs, and internal services without placing you in a shared public pool. Lens Chain mainnet uses chain ID 232, supports HTTP JSON-RPC and WebSocket access, and uses GHO as the gas token. Lens is built on the Matter Labs ZK Stack, so a Lens node is closer to serious application infrastructure than a simple endpoint URL.

Can I run a Lens validator node?

Not in the staking sense. Lens Chain is a ZK Stack Layer 2 with a centralized sequencer, so there is no permissionless, stake-to-earn validator like Ethereum or Solana. Block production and proof submission are handled by the sequencer and prover that settle to Ethereum. What we provision is a fast, dedicated full or archive RPC node (a ZKsync External Node), which is what apps, indexers, and dashboards actually need.

Do I need Ethereum L1 access to run a Lens RPC node?

Yes. Lens Chain settles to Ethereum, so your External Node must connect to an Ethereum L1 RPC endpoint to follow the parent chain and verify state. If that L1 endpoint is slow or rate-limited, your Lens node can fall behind, which shows up as stale reads and delayed indexing. You can bring your own Ethereum endpoint or run Ethereum on dedicated servers with us, ideally in the same region for tighter latency and faster catch-up.

Does Lens support both HTTP and WebSocket RPC?

Yes. Lens supports both HTTP JSON-RPC and WebSocket RPC. In the official node setup, the HTTP API is exposed on port 3060 and the WebSocket API on port 3061. We treat that as a practical split: HTTP handles standard reads and writes, while WebSocket is what you want for live subscriptions, event listeners, and real-time product behavior.

What is the difference between a full Lens node and an archive Lens node?

A full node is the right fit for most production apps that need current chain state, transaction submission, and normal read traffic. An archive node is for teams that need the entire rollup history, broader historical access, or advanced workloads such as proof-related queries. Lens says archive mode requires more resources, uses a Postgres dump, and should have pruning disabled. In plain terms, full nodes run apps, while archive nodes support deeper data and research workloads.

How much CPU, RAM, and storage do I need to run a Lens RPC node?

Lens sets the minimum for a standard mainnet node at a modern CPU, 32 GB RAM, 700+ GB of storage, and a 100 Mbps connection, with 1 Gbps+ recommended. For archive, Lens moves to about 16 cores, 64 GB RAM, and 2 TB of storage, with the state continuing to grow. We usually size above the minimum for production because real workloads include app traffic, indexing, retries, and operating headroom. That is where a Lens RPC provider on dedicated hardware makes more sense than a tight shared plan.

When do I need archive access or zks_getProof support?

You need archive access when your product depends on deeper historical data, full rollup history, or proof-related workflows that a standard node is not built to serve well. Lens also documents that if you require zks_getProof, the first archive bootstrap can need about 1 TB of RAM temporarily because the initial tree rebuild is very large. We only recommend that path when your workload actually needs it, because it changes both hardware planning and operating cost.

Can I keep my Lens RPC endpoint private with firewall rules and IP allowlisting?

Yes. We support private endpoint patterns for dedicated RPC deployments, including firewall rules and IP allowlisting. That gives you a cleaner security boundary for internal services, partner access, staging traffic, or controlled production exposure. Our view is simple: your Lens RPC should only be visible to the systems and teams that actually need it.

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

Lens Developer Resources

Official Lens 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 Lens 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