SolBurn Engine
Get automated buy-and-burn running on Solana in under an hour. Follow every step in order. No experience with Solana tools or Linux required.
What SolBurn Engine Does
SolBurn Engine is a program that automatically destroys (burns) your Solana token on a schedule. Burning tokens permanently removes them from circulation, reducing the total supply over time.
It runs 24/7 in the background on a Linux machine — like a Raspberry Pi or a VPS. Set it up once and it handles everything automatically.
| PHASE 1 | Burns tokens already sitting in your wallet. Free to run — no SOL spending required. |
| PHASE 2 | When your wallet runs out of tokens, automatically buys more with SOL and burns them. Runs forever as long as there is SOL in the wallet. |
167+ successful burns and 4M+ tokens destroyed on Solana mainnet. This is not a demo or prototype.
Before You Start
Get everything on this list ready before you begin. It will save you time.
- A Linux machine — Raspberry Pi 4, a VPS ($4/month on DigitalOcean or Vultr), or any Linux server
- Your token's mint address — find it on solscan.io or dexscreener.com
- A Solana wallet keypair file (.json) — dedicated burn wallet, not your main wallet
- At least 0.1 SOL in that wallet to cover fees and Phase 2 cycles
- A free Helius RPC endpoint — sign up at helius.dev
- Access to the private GitHub repo (contact @ABase9719 on X to be added)
Do not use your main personal wallet. Create a fresh wallet just for the burn engine and only fund it with what you need.
Getting your Helius RPC URL
Go to helius.dev, create a free account, click Create API Key, and copy the RPC URL. It looks like:
https://mainnet.helius-rpc.com/?api-key=YOUR-KEY-HERE
Getting your wallet keypair file
If you created your wallet with the Solana CLI, it is at ~/.config/solana/id.json by default. To create a fresh wallet just for burning:
solana-keygen new --outfile ~/burn-wallet.json
Step 01 — Connect to the Machine
If you are using a Raspberry Pi or remote VPS, open PowerShell (Windows) or Terminal (Mac/Linux) on your computer and run:
# Replace with your machine's IP address
ssh pi@YOUR.PI.IP.ADDRESS
# For a VPS it might look like:
ssh root@192.168.1.100
Type yes if asked about fingerprints, then enter your password. You are now inside the machine.
Just open a terminal. Skip this step.
Step 02 — Install Node.js
Check if Node.js is already installed:
node --version
If you see v18.x.x or higher, skip to Step 3. If you get "command not found":
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt-get install -y nodejs
# Confirm:
node --version
You should see something like: v20.11.0
Step 03 — Clone the Repository
git clone https://github.com/sampsonc37-hub/solburn-engine.git
cd solburn-engine
npm install
The npm install step downloads all dependencies. It may take a minute. When done you will see: added X packages.
The repository is private. Contact @ABase9719 on X with your GitHub username to be added as a collaborator.
Step 04 — Add Your Wallet File
# Replace path and IP with your own
scp ~/burn-wallet.json pi@YOUR.PI.IP.ADDRESS:/home/pi/burn-wallet.json
Do not put it inside the solburn-engine folder. Keep it in your home directory (/home/pi/) and never commit it to GitHub.
Step 05 — Configure
cp config.example.json config.json
nano config.json
Use arrow keys to move around. Edit text normally. When done: Ctrl+O to save → Enter → Ctrl+X to exit.
Required config fields
| Field | Example | What it means |
|---|---|---|
| tokenMint | cHJThV7z... | Your token's mint address |
| rpcEndpoint | https://mainnet.helius... | Your Helius RPC URL |
| walletPath | /home/pi/burn-wallet.json | Full path to your keypair file |
| burnIntervalMs | 300000 | How often to burn (ms). 300000 = every 5 min |
| phase2.enabled | true | Enable automatic buy-and-burn |
| phase2.solPerBurn | 0.01 | SOL to spend per Phase 2 cycle |
| tokenStandard | token-2022 | Use token-2022 or spl for legacy tokens |
| dashboardPort | 3333 | Local dashboard port |
Check on solscan.io — it shows the standard on your token's page. If created in 2024+, it is almost certainly token-2022.
Step 06 — Test Run
node index.js
You should see output like this within a few seconds:
[ENGINE] Config loaded
[ENGINE] Token: cHJThV7z...
[ENGINE] Wallet: 4keacT9C...
[ENGINE] Dashboard running at http://localhost:3333
[ENGINE] Phase 1 starting — checking wallet balance...
[ENGINE] Found 500,000 tokens — burning...
[ENGINE] BURNED ✓ TX: pvaoVN6Z...
If you see BURNED with a TX id, the engine is running. Verify on solscan.io by pasting the TX id. Press Ctrl+C to stop — then move to Step 7.
Common errors
| Error | Fix |
|---|---|
| RPC error / 429 | Helius rate limit. Wait a minute and retry, or upgrade your plan. |
| Invalid keypair | walletPath in config.json is wrong. Double-check the path. |
| Token not found | tokenMint is incorrect. Copy it again from Solscan. |
| Insufficient SOL | Top up the wallet with at least 0.05 SOL before Phase 2. |
Step 07 — Run as a Service
sudo nano /etc/systemd/system/solburn.service
Paste this — update the paths and username to match your setup:
[Unit]
Description=SolBurn Engine
After=network.target
[Service]
Type=simple
User=pi
WorkingDirectory=/home/pi/solburn-engine
ExecStart=/usr/bin/node /home/pi/solburn-engine/index.js
Restart=on-failure
RestartSec=10
StandardOutput=journal
StandardError=journal
[Install]
WantedBy=multi-user.target
Run whoami — it prints your username. Replace pi in the service file with whatever it shows.
Save the file (Ctrl+O, Enter, Ctrl+X), then:
sudo systemctl daemon-reload
sudo systemctl enable solburn
sudo systemctl start solburn
# Confirm it is running:
sudo systemctl status solburn
Status should show active (running). The engine is now burning on schedule. Check the dashboard to confirm.
The Dashboard
Once the service is running, open a browser and go to:
# From the machine itself:
http://localhost:3333
# From another device on the same network:
http://YOUR.PI.IP.ADDRESS:3333
Run hostname -I on the machine to find its IP address.
The dashboard shows burn count, total tokens burned, SOL spent, recent transactions, and a manual burn trigger.
Phase 2 — Buy and Burn
Phase 2 activates automatically when the wallet runs out of tokens. The engine buys via Jupiter V6, falls back to PumpPortal if needed, waits for settlement, then burns immediately.
Each Phase 2 cycle costs roughly 0.011 SOL (0.01 for the buy + ~0.001 in fees). Phase 2 pauses if the wallet runs out of SOL.
Live Stats on Your Website
SolBurn Engine can push burn stats to a Cloudflare Worker so your website shows live burn counts. Add this to config.json:
"cloudflare": {
"enabled": true,
"workerUrl": "https://your-worker.workers.dev/burn_stats",
"pushIntervalMs": 60000
}
Contact @ABase9719 on X. The Cloudflare Worker setup takes about 10 minutes.
Troubleshooting
| Problem | What to do |
|---|---|
| Service shows failed | Run sudo journalctl -u solburn -n 50 to see the last 50 lines of logs. |
| Jupiter failed → PumpPortal | Normal fallback. Only a problem if both fail. |
| 429 Too Many Requests | Helius rate limit. Increase burnIntervalMs or upgrade your Helius plan. |
| Cannot find wallet file | Run ls -la /home/pi/ to confirm the file is there. Fix the path in config. |
| Settlement timeout | RPC is slow. Try a different Helius endpoint or increase settlementTimeoutMs. |
| Not enough SOL | Top up the wallet. Need at least 0.02 SOL per Phase 2 cycle to be safe. |
| Dashboard not loading | Run sudo systemctl status solburn to confirm the service is up. |
| Token-2022 burn failing | Make sure tokenStandard is set to token-2022 in config.json. |
Quick Reference
# Check if service is running
sudo systemctl status solburn
# View live logs
sudo journalctl -u solburn -f
# Restart the service
sudo systemctl restart solburn
# Stop / start
sudo systemctl stop solburn
sudo systemctl start solburn
# Check wallet SOL balance
solana balance /home/pi/burn-wallet.json
Stuck? Reach out directly on X: @ABase9719. Every tool sold by CustodianTech comes with direct support from The Custodian.