Terminal and harkctl

Advanced. You never need the terminal to use your bots. It's there for people who like to look under the hood: everything in the app can also be done here, plus a few things that are deliberately terminal-only, such as backing up a wallet's private key.

Turn on the Advanced switch to see the server's Terminal page. It has the SSH command to copy, your SSH keys, the server's host key fingerprints and this command list.

Signing in with SSH

Your server accepts SSH keys only. There is no password to guess or leak. You sign in as the ubuntu user (ssh ubuntu@<your server's address>); signing in as root is turned off. Commands that need root use sudo.

1. Add your public key on the Terminal page (Add an SSH key). Paste the public half, the line that starts with ssh-ed25519 or ssh-rsa, usually from a file ending in .pub. Never paste a private key; the page refuses one.
2. Copy the SSH command from the top of the Terminal page and run it in your own terminal.
3. Check the host key the first time (below).

You don't need a key at checkout; add one whenever you want terminal access. Keys you add on the Terminal page replace each other as a set; keys added on the server with harkctl ssh-keys add are kept separately.

Create an SSH key

An SSH key comes in two halves: a private key that stays on your computer, and a public key you give to your server. If you already have one, the public half is in a file ending in .pub in the .ssh folder of your home directory.

To make a new one, open a terminal (on Windows 10 or 11, PowerShell) and run:

ssh-keygen -t ed25519 -C "you@laptop"

Press Enter to keep the default file, and set a passphrase if you want one. Then show the public half:

cat ~/.ssh/id_ed25519.pub

On Windows PowerShell: Get-Content $env:USERPROFILE\.ssh\id_ed25519.pub. Copy the single line it prints, starting ssh-ed25519, and paste it at checkout or on the Terminal page. Never share the file without .pub: that is your private key.

Check the host key fingerprint

The first time you connect, SSH shows the server's host key fingerprint and asks whether to trust it. It looks like SHA256: followed by a string of letters and numbers.

Compare it with the Host keys on the Terminal page (ED25519 and ECDSA). Answer yes only if it matches one of them exactly. If it doesn't match, don't connect, and contact us: something is between you and your server.

The page also shows the bot agent's fingerprint. On the server, harkctl agent fingerprint should print the same one.

harkctl

harkctl is the command-line tool on every bots server. It talks to the bot agent on the server, so the same rules apply as in the app: going live and moving money need your PIN, and limits are enforced by the bot.

<bot> is sniper (Solana Block-0 Sniper) or momentum (Solana Momentum Sniper). harkctl needs root, so run it with sudo, for example sudo harkctl status. Run harkctl --help, or harkctl <command> --help, for the full options of any command.

Things that work only here

• Importing and exporting a wallet's private key. Keys never go through the web. Export asks for your PIN.
• The withdrawal allowlist. Addresses added with harkctl withdraw-allowlist add are active at once, because only someone signed in to your server can add them. Addresses saved in the app wait 24 hours instead.
• Installing or rolling back bot versions, and managing SSH keys and support access from the server itself.

Config from the terminal

harkctl config edit opens the running config in your editor and saves it as a new version; validate, diff and apply let you work from a file. Every save, from the web, support or the terminal, is a version, and harkctl config history shows who saved each one and from where. The web app sees terminal changes straight away. The settings are listed in the Solana Block-0 Sniper and Solana Momentum Sniper references.

Command reference