Setup guide · GREEN / VOLUME · latest version

From registration to your first trade

Fifteen steps in order. Wallet setup and registration take about an hour; server setup takes another 20–30 minutes. Check off completed steps: your progress is saved in this browser.

≈ 1.5 hours9 walletsserver in Japan← home

Part 1

Registration

Complete this section for each wallet before its first trade.

01

Prepare your wallets

The bot trades across multiple wallets, with a paired position on each.

  1. Create separate EVM wallets using MetaMask, Rabby, or a similar app. The bot supports 1–9 wallets; more funded wallets can support more turnover.
  2. Use separate wallets rather than Hyperliquid subaccounts. Referral eligibility for subaccounts differs.
  3. Record each wallet address. Keep seed phrases offline and private: the bot does not need them.
!
One wallet, one bot. Do not run the same wallet on another server or bot: the processes can interfere with each other.
02

Link each wallet to Entropy using the link

The io leg trades through Entropy. Use cryptogains to join the referral program; tier and rebate benefits depend on current terms.

https://entropy.io/?r=cryptogains
  1. Open the link and connect your first wallet.
  2. Complete enrollment and sign the wallet message if prompted.
  3. Confirm that the website shows the wallet as enrolled.
  4. Repeat for the remaining wallets.
!
Use both of our referral codes: cryptogains on Entropy and CRYPTOGAINS on Hyperliquid. Without confirmed Entropy referral access, the bot will not open new trades. If you have not linked the codes manually, builds with auto-binding enabled will try to apply missing referrals and verify the result. This can fail: an existing referrer is not replaced, and automatic Entropy enrollment requires the main wallet key, not an API-agent key. You can instead complete enrollment manually in the official interfaces. Never send keys to this website. Hyperliquid referral binding is separate from the Entropy entry check.
03

Deposit through Entropy

The bot uses USDC on Hyperliquid and sizes trades according to balance. Recommended balance per account: VOLUME — $150 USDC; GREEN — $250 USDC. You can deposit less: trade sizes and available turnover will be limited by your balance and minimum order sizes. This is a setup guideline, not a profit guarantee.

Main option: through Entropy:

  1. On entropy.io connect your wallet and select funding (Deposit).
  2. Deposit USDC and wait for it to arrive.
  3. Repeat for every wallet.
!
Check the current network and minimum deposit in the official deposit screen before sending funds. Fund wallets only with capital you intend to use for trading.
04

Register each wallet on Hyperliquid using the link

Our recorded wallets showed fees of 0.864 bps versus 0.900 without CRYPTOGAINS. The discount and volume limit remain subject to Hyperliquid's current referral rules.

https://app.hyperliquid.xyz/join/CRYPTOGAINS
!
First complete your deposit through Entropy and wait for it to be credited. Do not try to activate the Hyperliquid referral code before funding. If you see “Need to Deposit”, finish step 03 and check your balance.
  1. Open the link in the browser connected to your first wallet.
  2. Click Connect, select your wallet, and sign in.
  3. Confirm CRYPTOGAINS if the website prompts you.
  4. Check that app.hyperliquid.xyz/referrals shows CRYPTOGAINS.
  5. Disconnect the wallet, connect the next one, and repeat for each wallet.
×
Set the referral before the wallet's first trade. If it has already traded, check eligibility with Hyperliquid; a new wallet may be required.
05

TRADE.XYZ: no separate trading account needed

The xyz markets, such as xyz:SNDK, belong to TRADE.XYZ on Hyperliquid. The bot uses the same Hyperliquid account.

  • The xyz leg records trading volume against your wallet, comparable to the Entropy leg.
  • If TRADE.XYZ announces a rewards program, follow its requirements, such as connecting wallets on its website.
i
Venues control rewards and airdrops. We do not promise them. The bot creates market activity; participation depends on your choice and the venue's rules.
06

A signing key for each wallet

The bot needs the wallet address and an order-signing key: either the owner's key or a Hyperliquid API-agent key. Referral verification may separately require owner authentication.

Option A: wallet private key. Export the private key in your wallet settings (MetaMask: Account details → Show private key). You do not need to create an API agent for this option.

Option B: API-agent key. An agent can trade but cannot withdraw funds:

  1. Open app.hyperliquid.xyz/API and connect your wallet.
  2. Enter an agent name, such as green-1, then click Generate.
  3. Copy the agent's private key: it is shown only once.
  4. Click Authorize API Wallet and sign in your wallet.

For each wallet, record a pair: wallet address + key.

!
Do not enter a seed phrase. Store keys in a password manager, not in chat messages or ordinary notes.

Part 2

Server

The bot runs continuously on a rented Linux server. Your personal computer does not need to stay on.

07

Rent a server

Choose a location with low measured latency to Hyperliquid. Japan is the recommended starting location in this setup.

https://console.surfercloud.com/light-server/create/
SettingChoose
RegionJP (Tokyo), Japan
Plan2Core4G · 2 CPU cores, 4 GB RAM, 80 GB disk
Operating systemSystem Image → Ubuntu 24.04 64bit

After creating the server, the provider shows its IP address, username (usually ubuntu or root), and login details.

Select JP Tokyo, Ubuntu 24.04 and 2Core4G
1. Region: JP (Tokyo). 2. System Image → Ubuntu 24.04 64bit. 3. General → 2Core4G: 2 CPU cores, 4 GB RAM, 80 GB disk, 800 GB traffic. The screenshot shows $9/month; check the current price before paying.
Login configuration and firewall preset
4. Login: ubuntu; generate and safely store a unique password. 5. More Settings → Security Rule: the screenshot uses “Web service recommendation: tcp 22,3389,80,443”. Keep the firewall enabled. For Ubuntu, port 3389 (Windows RDP) is unnecessary: remove it from your custom rule. Allow TCP 22 only from your IP; TCP 80/443 are for a public HTTPS dashboard. Never expose port 8765 or open all ports. If your installer uses a different gateway port, open only that documented port.
08

Connect and change your password

Open Terminal on Mac or Linux, or PowerShell on Windows.

on your computer
ssh ubuntu@SERVER_IP

Replace SERVER_IP with the address from step 7 and log in. A connected server prompt looks like:

ubuntu@entropy-green:~$
on the server · enter the new password twice; characters stay hidden
sudo passwd ubuntu
09

Download the archive directly on your server

Recommended: run the download command in your SSH session from step 8. No download to your computer or SCP transfer is needed.

Choose GREEN or VOLUME and run only the matching commands below on the server. These commands do not install or start the bot. Do not run both versions with the same wallet.

The supplied URLs use HTTP, not encrypted HTTPS. The links always point to the latest version. Before extracting, compare the archive's SHA-256 (sha256sum entropy-green-latest.tar.gz) with the checksum from the owner's message; all checksums are in SHA256SUMS, signed with the update-channel key.

GREEN

On the server · download
cd ~ && curl -fL --output entropy-green-latest.tar.gz.part https://entropybot.app/get/entropy-green-latest.tar.gz && mv entropy-green-latest.tar.gz.part entropy-green-latest.tar.gz
On the server · unpack and enter the folder
cd ~
rm -rf entropy-green && mkdir entropy-green && tar xzf entropy-green-latest.tar.gz -C entropy-green --strip-components=1 && cd entropy-green

VOLUME

On the server · download
cd ~ && curl -fL --output entropy-volume-latest.tar.gz.part https://entropybot.app/get/entropy-volume-latest.tar.gz && mv entropy-volume-latest.tar.gz.part entropy-volume-latest.tar.gz
On the server · unpack and enter the folder
cd ~
rm -rf entropy-volume && mkdir entropy-volume && tar xzf entropy-volume-latest.tar.gz -C entropy-volume --strip-components=1 && cd entropy-volume

Next, continue to step 10. GREEN uses install-green.sh; VOLUME uses install-volume.sh.

Alternative: upload from your computer

Download one archive with the buttons above. Run the matching SCP command on your computer from the folder containing the file; replace SERVER_IP with your server address. Then return to SSH and use the extraction command above.

On your computer · in the folder containing the archive
scp entropy-green-latest.tar.gz ubuntu@SERVER_IP:~
On your computer · in the folder containing the archive
scp entropy-volume-latest.tar.gz ubuntu@SERVER_IP:~

If curl is not installed: sudo apt-get update && sudo apt-get install -y curl.

Part 3

Install and launch

Before you explicitly enable live trading in step 12, setup does not place trading orders.

10

Install with one command

The installer retrieves the machine number, markets, and entry windows.

GREEN
sudo bash install-green.sh
VOLUME · instead of the GREEN command
sudo bash install-volume.sh

Use only the commands labelled for your installed version. GREEN and VOLUME have separate services, configuration and dashboards; never share a wallet between them.

The script asks for the wallet count, then each address and key from step 6. Key input stays hidden and is stored in GREEN: /opt/entropy-green/.env · VOLUME: /opt/entropy-volume/.env with permissions 600.

The installer then:

  • installs dependencies and clock synchronization;
  • checks archive integrity and performs an offline program check;
  • creates a dedicated user entropy (GREEN), entropyvol (VOLUME) and systemd services;
  • retrieves the build and machine settings, checks wallet configuration, and prints markets and entry windows.
Import wallets from a file

Create ~/wallets.txt with one wallet per line: address and key separated by a space. Install using it, then remove the temporary key file:

GREEN

nano ~/wallets.txt
sudo bash install-green.sh --wallets-file ~/wallets.txt
shred -u ~/wallets.txt

VOLUME

nano ~/wallets.txt
sudo bash install-volume.sh --wallets-file ~/wallets.txt
shred -u ~/wallets.txt
!
Do not include key files in the release archive or leave temporary copies on the server.
11

Verify the installation

GREEN

sudo bash /opt/entropy-green/install-green.sh --status

VOLUME

sudo bash /opt/entropy-volume/install-volume.sh --status

This command displays the version, entry windows, markets, service state, and recent logs. Check for wallet startup errors.

12

Enable trading

This step enables real trading orders.

GREEN

sudo bash /opt/entropy-green/install-green.sh --live

VOLUME

sudo bash /opt/entropy-volume/install-volume.sh --live

The script checks the settings again and asks you to type the exact Russian confirmation ДА. The bot and dashboard then start, with automatic service restart after failures and server reboots.

● entropy-green.service - Entropy GREEN trading bot
     Active: active (running)

Trades occur when qualifying spreads appear. Timing varies; nights and weekends may be quieter. Before launch, the account must be in Unified Account mode with sufficient collateral.

13

Open the dashboard

The dashboard listens locally on the server. Access it through an SSH tunnel.

on your computer · use a new terminal window and keep it open

GREEN

ssh -L 8765:127.0.0.1:8765 ubuntu@SERVER_IP

VOLUME

ssh -L 8766:127.0.0.1:8766 ubuntu@SERVER_IP

Then open GREEN: http://127.0.0.1:8765 · VOLUME: http://127.0.0.1:8766 in your browser. The dashboard shows positions, balances, turnover, and updates.

i
The installer can also expose an authenticated gateway: GREEN on port 8443, VOLUME on port 8444. Use the login printed by the installer. Do not expose internal ports 8765/8766. If the browser cannot verify the gateway certificate, use the SSH tunnel rather than bypassing the warning.

GREEN · show login

sudo bash /opt/entropy-green/install-green.sh --show-login

VOLUME · show login

sudo bash /opt/entropy-volume/install-volume.sh --show-login

Part 4

Daily checks

The bot runs continuously. Check its status regularly.

14

What to check

WhatWhereExpected behavior
Service running--statusactive (running)
Daily turnoverdashboardusually higher on weekdays; historical weekends were 2–4 times quieter
Open positionsdashboard or Hyperliquidpaired legs; contact support if an unmatched leg persists for more than a few minutes
Venue turnoverEntropy and TRADE.XYZapproximately equal
Live logsGREEN: sudo journalctl -u entropy-green -f · VOLUME: sudo journalctl -u entropy-volume -fCtrl+C to exit
15

Updates

The update workflow checks existing positions before switching versions.

Release announcements and bot updates in our Telegram channel: @entropyb0t ↗.

  1. Dashboard → Updates → Check for updates.
  2. If a new version is available, click Update.

The updater verifies the signature and checksum, pauses new entries, waits for active trades to finish, and restarts. If the candidate fails, it restores the previous version.

equivalent terminal commands

GREEN

sudo bash /opt/entropy-green/install-green.sh --update-check
sudo bash /opt/entropy-green/install-green.sh --update-now

VOLUME

sudo bash /opt/entropy-volume/install-volume.sh --update-check
sudo bash /opt/entropy-volume/install-volume.sh --update-now

Help

Troubleshooting

Stop automated trading — GREEN / VOLUME

GREEN

sudo sed -i 's/^LIVE_TRADING=.*/LIVE_TRADING=false/' /opt/entropy-green/.env
sudo systemctl restart entropy-green

VOLUME

sudo sed -i 's/^LIVE_TRADING=.*/LIVE_TRADING=false/' /opt/entropy-volume/.env
sudo systemctl restart entropy-volume

Use this only after checking that the selected account has no open positions or orders. This disables automated trading, including protective position management; it is not an entry-only pause. Do not use it to leave positions unmanaged. To enable trading again, use step 12.

A key was exposed
  1. If an agent key was exposed, revoke the agent at app.hyperliquid.xyz/API and create a replacement (step 6). If the owner's private key was exposed, secure the funds using a new wallet.
  2. Open the configuration: GREEN: sudo nano /opt/entropy-green/.env · VOLUME: sudo nano /opt/entropy-volume/.env.
  3. Replace the affected wallet key: wallet 1 uses HYPERLIQUID_AGENT_PRIVATE_KEY=; wallets 2–9 use WALLET_2_AGENT_PRIVATE_KEY= … WALLET_9_AGENT_PRIVATE_KEY=.
  4. Save with Ctrl+X, Y, Enter. Restart with: GREEN: sudo systemctl restart entropy-green · VOLUME: sudo systemctl restart entropy-volume.
The server rebooted

Enabled services start automatically. For each installed version, run its status command from step 11 and verify that position recovery completed.

Uninstall the bot

Before uninstalling, verify that the selected wallets have no open positions or orders. Uninstalling stops their management and does not close exchange positions. Run only the command for the product you intend to remove.

GREEN

sudo bash /opt/entropy-green/install-green.sh --uninstall

VOLUME

sudo bash /opt/entropy-volume/install-volume.sh --uninstall

A configuration backup remains in GREEN: /root/entropy-green-backup-* · VOLUME: /root/entropy-volume-backup-*. It contains keys; keep it protected and do not share it. The machine identity is retained for reinstallation. The other product is not removed. Do not add --purge for ordinary removal.

Error messages and next steps
MessageAction
“archive built for …, server is …”Request an installer matching the server architecture
“checksum mismatch”Download the archive again (step 9)
“settings check failed”Check addresses and keys in GREEN: /opt/entropy-green/.env · VOLUME: /opt/entropy-volume/.env, then run --status
“update channel not configured”--set-channel URL — request the channel URL from us
“manifest signature verification failed”No update was installed. Contact support
“restored version …”The candidate failed and the previous version is running. Send the sanitized log from GREEN: /var/log/entropy-green-update.log · VOLUME: /var/log/entropy-volume-update.log
Service repeatedly restartingSend sanitized output from GREEN: sudo journalctl -u entropy-green -n 100 · VOLUME: sudo journalctl -u entropy-volume -n 100
Server clock inaccuratetimedatectl should show System clock synchronized: yes
What to send to support

GREEN

sudo journalctl -u entropy-green -n 100 --no-pager
sudo bash /opt/entropy-green/install-green.sh --status

VOLUME

sudo journalctl -u entropy-volume -n 100 --no-pager
sudo bash /opt/entropy-volume/install-volume.sh --status

Describe the issue and send sanitized output from these commands. Review logs before sharing them.

×
Never send anyone GREEN: /opt/entropy-green/.env · VOLUME: /opt/entropy-volume/.env, backups from GREEN: /root/entropy-green-backup-* · VOLUME: /root/entropy-volume-backup-*, private keys, seed phrases, or sensitive wallet screenshots. We will never ask for them.

Ready to start?

Support, partnership proposals and bot updates: @entropyb0t ↗.