Web3
Solana nodes, streams and the proxies around them
Dedicated RPC, Yellowstone Geyser gRPC and validator-tuned metal, on the same account and the same invoice as the proxy pools.
Nodes
Four ways to get on chain
Start on the shared endpoint to build against, then move to a dedicated node when the rate limit starts shaping your architecture.
Shared RPC
A private key on a pooled endpoint
- Rate limit
- 150 requests / second
- Chains
- All supported chains
- Methods
- Full JSON-RPC, no method filter
- Websockets
- Included
- Your own API key
- Usage dashboard
- No archive data
- Shared with other tenants
Dedicated Solana RPC
One node, one tenant, no neighbors
- Hardware
- EPYC 9254, 24 cores
- Memory
- 768 GB DDR5 ECC
- Storage
- 2 x 7.68 TB NVMe
- Uplink
- 10 Gbps unmetered
- No rate limit beyond the hardware
- getProgramAccounts allowed
- Snapshot restore included
- Choice of region
Geyser gRPC
Account and slot updates as they land
- Stream
- Yellowstone gRPC
- Filters
- Account, owner, slot, transaction
- Latency
- Sub-slot from the validator
- Uplink
- 10 Gbps unmetered
- Dedicated stream, not a fan-out
- Pairs with a dedicated RPC node
- Backfill from snapshot on request
- TLS and token auth
Validator metal
Tuned for consensus, not for web serving
- Hardware
- Ryzen 9 9950X, 16 cores
- Memory
- 384 GB DDR5 ECC
- Storage
- 3 x 3.84 TB NVMe
- Uplink
- 10 Gbps unmetered
- Separate ledger and accounts drives
- Kernel and network tuning applied
- IPMI and remote power
- You keep your own keys
Drop-in
A URL and a key, same as any other RPC
Nothing to rewrite. Point your existing client at the endpoint and carry on.
curl https://rpc.foidproxy.com/solana \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_KEY" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "getSlot"
}'
# {"jsonrpc":"2.0","result":312884109,"id":1}import { Connection, PublicKey } from "@solana/web3.js";
const connection = new Connection(
"https://rpc.foidproxy.com/solana?key=YOUR_KEY",
{ commitment: "confirmed", wsEndpoint: "wss://rpc.foidproxy.com/solana" },
);
const slot = await connection.getSlot();
const balance = await connection.getBalance(new PublicKey(WALLET));
console.log(slot, balance / 1e9);Workflows
What people point this at
Most of it is the node and the proxy pool working together rather than either one on its own.
Mints and drops
A dedicated RPC node means your transactions are not queued behind everyone else on a public endpoint. Pair it with residential proxies when the mint site itself is the thing fighting you.
On-chain indexing
Geyser gRPC pushes account and slot updates to you instead of making you poll. Cheaper than hammering getProgramAccounts and a lot closer to real time.
Latency-sensitive trading
Pick a region next to the leader schedule you care about. Ashburn, Frankfurt, Amsterdam and Tokyo are all on the list.
Wallet isolation
One static ISP proxy per browser profile keeps wallet sessions cleanly separated, which matters on any front end that fingerprints the connection.
Price and liquidity monitoring
Watch DEX pools, orderbooks and aggregator quotes across chains. The datacenter pool is the fast way to poll public APIs alongside your own node.
Analytics and research
Archive access, full JSON-RPC and no method filter, so the awkward calls other providers block are simply available.
Chains we serve
Solana gets the dedicated hardware and the Geyser stream. The rest are RPC and archive endpoints on the shared plan.
- SolanaRPC, Geyser, validator
- EthereumRPC and archive
- BaseRPC
- ArbitrumRPC
- BNB ChainRPC
- PolygonRPC
- AvalancheRPC
- SuiRPC
- BitcoinFull node
Where the nodes sit
Pick the region nearest the validators or users you care about. We confirm the region with you before the node is set up.
Questions
Web3 FAQ
One thing worth stating plainly: we host infrastructure. We do not custody funds, sign transactions or hold keys.
Not yet. Payment is by card through Stripe today. Crypto payment is planned, and this page will say so when it is live.
Yes. One tenant per machine. Nobody else holds an API key against it and nobody else is consuming its IOPS while you are trying to read accounts.
Not on dedicated nodes. It is heavy, which is exactly why shared providers block it, and exactly why people rent a node of their own.
No. We provide tuned hardware, the network and remote hands. You run the process and you hold your own keys. We never ask for them and we cannot sign anything on your behalf.
Yes, and that is the usual pairing. The gRPC plan can sit alongside a dedicated RPC node so your indexer streams while your app queries.
Ethereum, Base, Arbitrum, BNB Chain, Polygon, Avalanche, Sui and Bitcoin. Solana is where the dedicated hardware and the Geyser stream are; the rest are RPC and archive.
Tell us what you are building
Indexer, trading stack, mint infrastructure or a validator. We will tell you which node fits and whether you actually need the expensive one.
Accounts are for adults 18 and over. Buying means agreeing to the Terms and Acceptable Use Policy.