Private NeuroWeb RPC Endpoints on a Dedicated Node

NeuroWeb is a permissionless, EVM-enabled Polkadot parachain that powers the OriginTrail Decentralized Knowledge Graph (DKG) for AI, incentivizing knowledge creation and sharing through knowledge mining. It is the rebrand of the former OriginTrail Parachain, approved by community governance in December 2023. Its native token is NEURO, and it is secured by the Polkadot relay chain.

One node serves both. NeuroWeb is an EVM-enabled Polkadot parachain that runs an Ethereum-compatible EVM (Frontier) on top of its Substrate runtime. Your dedicated node exposes the Substrate JSON-RPC (chain_, state_, system_, author_) and the Ethereum JSON-RPC (eth_*) over the same HTTP and WSS endpoints, so Polkadot.js and Web3/ethers tooling both connect without extra infrastructure.

Most teams start with a pruned full NeuroWeb node because it serves current-state reads and transaction submission with far lower storage needs. Choose archive when your product must query full history, power explorers, run deep analytics, or support heavy historical lookups across EVM and Substrate state. If you are unsure, tell us your workload, and we will map you to the right node type.

A shared NeuroWeb RPC provider runs many customers on pooled infrastructure. That can create unpredictable latency during spikes, plus shared rate limits and noisy-neighbor slowdowns. Dedicated NeuroWeb RPC node servers give you single-tenant resources, your own access rules, and clearer fault boundaries. You control performance and security instead of inheriting someone else's traffic.

Yes. NeuroWeb collators produce parachain blocks and require fast hardware: high-clock CPU cores and NVMe SSD storage, since slower disks cannot keep up with block production. We provision single-tenant NVMe bare metal, you hold the session keys, and you get full root, KVM, and IPMI for fast recovery. Finality still comes from the Polkadot relay chain, so collators focus on block production and uptime.

Provisioning is fast. The real variable is sync time. Sync depends on chain state, node type, storage speed, and network conditions. A pruned full node usually reaches a usable state earlier than an archive setup because an archive has far more data to process. As a parachain, NeuroWeb syncs against the Polkadot relay chain, and we deploy from current snapshots where possible so you skip the long cold sync.

You can expose the standard RPC and WebSocket ports used by Substrate-based nodes, plus the Ethereum JSON-RPC over HTTP and WSS. We recommend exposing only what you need. Many teams restrict access to known IPs, put a reverse proxy in front, and keep admin surfaces closed. With a dedicated server, you can define firewall rules that match your risk level and traffic profile.

Yes. That is a core benefit of running a dedicated NeuroWeb RPC node on dedicated servers. You can scale up resources as load grows, add storage for archive needs, and move to higher core counts for heavy concurrency. This keeps your endpoint stable while your product grows, without rebuilding everything on a new platform.

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.