Skip to main content
You can run a blockchain node on a FlashRDP Linux VPS as long as the chain fits on your plan’s disk: a pruned Bitcoin Core node fits on every plan, but full Ethereum and Solana nodes need far more storage than any FlashRDP plan offers. Running nodes is allowed; mining is not. Your own node lets you verify blocks yourself and broadcast transactions without relying on a third-party RPC provider’s rate limits.
Mining is not allowed. The Acceptable Use Policy prohibits cryptocurrency mining and any other sustained CPU use to generate cryptocurrency. Running blockchain nodes and trading bots is allowed.

​
Check that the chain fits

FlashRDP plans have between 50 GB (BRONZE) and 200 GB (EMERALD) of SSD storage. Compare that with the chain you want to run: Check each project’s documentation for current sizes before you deploy. For chains that don’t fit, use a hosted RPC provider or your own hardware for the node, and run your apps or bots on the VPS.

​
Run a pruned Bitcoin Core node

1

Deploy your server

Order a FlashRDP Linux VPS with Ubuntu 22.04 or 24.04. SILVER or above gives the initial sync more RAM. Wait for the email with your SSH login.
2

Update the system

3

Download and verify Bitcoin Core

Download the Linux x86_64 release, SHA256SUMS and SHA256SUMS.asc from bitcoincore.org. Check the archive against SHA256SUMS and verify the signatures as described on that page, then extract it and copy the programs from its bin folder to /usr/local/bin.
4

Configure pruning and upload limits

Create ~/.bitcoin/bitcoin.conf:
A node serves blocks to other peers, which counts towards your fair bandwidth policy allowance. maxuploadtarget keeps that in check.
5

Start the node

The first sync takes hours to days. verificationprogress in the output reaches 1 when it’s done.
Run the node as a non-root user and only expose its RPC port to 127.0.0.1. Bitcoin Core does this by default; don’t add rpcbind or rpcallowip lines that open RPC to the internet.

Run Crypto Trading Bots

Connect via SSH

Plans and Pricing

Acceptable Use Policy

Last modified on October 16, 2026