Running a full node.
Support the GlobalBoost network by running your own copy of the blockchain. A full node checks every block and transaction against the rules, so you never have to trust anyone else.
What is a full node?
A full node is a program that fully validates transactions and blocks. Almost all full nodes also help the network by accepting blocks and transactions from other nodes, checking them, and passing them on.
Most full nodes also serve lightweight clients by letting them send transactions to the network and telling them when a transaction affects their wallet. The more nodes there are, the harder GlobalBoost is to censor or shut down — there is no company or leader to switch off.
The GlobalBoost-Y software (globalboostd and the Qt wallet) is the reference full node, built on the Bitcoin Core code base.
Costs and warnings
Running a node is useful, but it has real costs. Read this before you start.
- Special cases: some internet providers, workplaces or countries restrict peer-to-peer traffic. Check before running a node that accepts incoming connections.
- Secure location: your node stores wallet keys if you use the built-in wallet. Only run it on a computer you trust, kept up to date and free of malware.
- Legal: using cryptocurrency may be restricted where you live. It's your responsibility to follow local law.
- Bandwidth: a node uploads blocks to peers. If you have a data cap, limit uploads (see configuration tuning).
- Privacy: other nodes can see your IP address. Consider running over Tor if this matters to you.
- Only download from the official source: GitHub releases. Fake wallets are a common scam.
Minimum requirements
GlobalBoost's chain is far smaller than Bitcoin's, so a modest computer or VPS is enough.
- Operating systemRecent Windows, or Linux (Ubuntu 22.04+ recommended)
- Disk20 GB of free space, ideally an SSD
- Memory2 GB of RAM (4 GB recommended)
- InternetBroadband with unlimited or generous upload
- UptimeAt least 6 hours a day; 24/7 is best
- Port8226 open for incoming connections (optional)
Windows instructions
- Download the Windows QT wallet from the BSTY Wallets page and unzip it.
- Run globalboost-qt.exe. On first launch, choose where to store the blockchain (the default is fine).
- Leave it open while it downloads and checks every block since 2014. The progress bar at the bottom shows how far it has got.
- If Windows Firewall asks, allow access on private networks so other nodes can connect to you.
To run a node without the wallet window, open Command Prompt in the same folder and start the daemon:
globalboostd.exe -daemonLinux instructions
Download the Linux release from GitHub, or build from source. Then start the daemon:
./globalboostd -daemon
./globalboost-cli getblockchaininfo # check sync progress
./globalboost-cli getconnectioncount # number of peersTo start the node automatically when the computer boots, add a cron entry:
crontab -e
# add this line (adjust the path):
@reboot /home/USER/globalboost/bin/globalboostd -daemonTo stop the node safely:
./globalboost-cli stopNetwork configuration
Your node works fine for yourself without this step. But to help the network, other nodes must be able to reach you on TCP port 8226.
- Give your computer a fixed local IP address in your router settings.
- In the router's port forwarding section, forward TCP port 8226 to that address.
- Allow the port in your firewall. On Linux with ufw:
sudo ufw allow 8226/tcpCheck it's working: after a while, getconnectioncount should report more than 8 peers, meaning others are connecting to you.
Never forward or expose the RPC port (8225) to the internet.
Configuration tuning
Settings go in globalboost.conf in your data folder — ~/.globalboost/ on Linux, %APPDATA%\GlobalBoost\ on Windows. Restart the node after changes.
Reduce storage — keep only recent blocks (in MB). Pruned nodes still fully validate, but can't serve old blocks:
prune=5000Reduce upload traffic — cap uploads per day (in MB):
maxuploadtarget=1000Reduce connections — fewer peers use less bandwidth and memory:
maxconnections=20Disable listening — only make outgoing connections:
listen=0Use less memory during sync:
dbcache=300Thank you for helping keep GlobalBoost decentralized.
Developer docs