Private Manta Pacific RPC Endpoints on a Dedicated Node

A dedicated Manta Pacific RPC node runs on single-tenant bare-metal hardware reserved for you: CPU, RAM, NVMe storage, and network port are yours alone. Shared RPC endpoints split capacity across many users, so when demand spikes they throttle requests or add latency. A dedicated setup avoids that and lets you control the full stack, from the op-geth execution client to the Ethereum L1 RPC connection.

Manta Pacific is an OP Stack L2 rollup. You run an execution client (op-geth) and a rollup node (op-node). The execution client handles state, transaction processing, and RPC queries; the rollup node derives L2 blocks. Manta Pacific uses Celestia for data availability, so you can optionally run a Celestia light node alongside op-node and op-geth, and you also need a reliable Ethereum L1 RPC endpoint. With full root access you install, configure, and update these on your own schedule.

Yes. Manta Pacific was the first Ethereum L2 to adopt Celestia as its modular data availability layer, which lowers transaction costs versus posting all data to Ethereum. The rollup still settles to Ethereum L1. When running a node, op-node can connect to a Celestia light node for data availability sampling, and we can provision that light node alongside your op-geth and op-node.

Yes. Manta Pacific is an OP Stack L2 that settles to Ethereum L1, so the op-node component reads from an Ethereum L1 RPC endpoint to verify batches and reconstruct the L2 chain. You can use your own Ethereum node or a reliable third-party L1 RPC. The quality of your L1 source directly affects whether your Manta Pacific node stays in sync.

A full node keeps current state and recent history and serves most RPC queries: balances, contract reads, receipts, and recent logs. An archive node retains full historical state at every block height, which is needed for eth_call at older blocks, historical balance lookups, and deep event-log scans. Archive needs significantly more storage and RAM, so choose full for standard production and archive when you need historical state.

Open the P2P ports your op-geth and op-node configuration uses for peer discovery and sync. Keep the RPC ports (HTTP 8545, WebSocket 8546, and the Engine API 8551) private until allowlists and rate limits are configured. Exposing RPC ports publicly without protection invites abuse, so put a reverse proxy with authentication or IP filtering in front before any external access.

Manta Pacific mainnet uses chain ID 169 and the Sepolia testnet uses chain ID 3441006. The native gas token is ETH, the same as Ethereum, while MANTA is the network's governance and utility token. Your node serves standard EVM JSON-RPC over HTTPS and WebSocket, so existing Ethereum tooling and libraries work without changes.

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.

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.

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.

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.