airdropbotpro/airdropbotpro-runner repository overview

⁠Airdrop Bot Pro Runner

The self-hosted execution client for Airdrop Bot Pro⁠. The runner lives on your own server, VPS or computer, picks up the jobs you schedule on the platform for your runner wallets, signs the transactions locally and sends them to EVM networks.

⁠Quick start

You do not need to write the command yourself.

1. Install Docker⁠ (Docker Desktop or Docker Engine).
2. Sign in at airdropbotpro.com⁠ and open the Runners page.
3. Click Add runner, reveal your runner key and copy the generated command.
4. Paste it into a terminal on the machine that will run the runner.

The command pulls this image, creates a named Docker volume, registers the runner with a one-time token and starts it in the background with --restart unless-stopped. Bind your runner wallets to it on the same page and it starts taking their jobs.

Running jobs requires an active plan that includes runners.

⁠Platforms

⁠Tags

• latest: the newest release. The command on the Runners page uses it.
• X.Y.Z (for example 1.0.19): immutable release tags. Pin one if you prefer to update by hand.

⁠Updating

Use the Update command for your runner on the Runners page. It pulls the new image and recreates the container; the data volume is kept, so the runner keeps its identity and does not need to register again.

⁠Data and backup

The runner keeps its encrypted state in a named Docker volume mounted at /data. Keep that volume: the Runners page offers export and restore commands for moving the runner to another machine.

⁠Security

• The image contains no keys, tokens or credentials. Your account's runner key is passed when the container starts (RUNNER_KEY).
• Wallet private keys are encrypted in your browser before they leave it. The runner decrypts them in memory only to sign the jobs of wallets you bound to it.
• Every execution plan is signed by the platform. Before signing, the runner checks that signature, the wallet, the chain and the plan's expiry, and it never pays more than the plan's signed fee limits.
• The platform also holds your runner key, so it can technically decrypt runner wallets. A database dump alone cannot.
• Treat RUNNER_KEY like a password: it is visible in shell history and docker inspect. If it leaks, rotate it on the Runners page; runners still on the old key stop taking work until restarted with the new command.
• The container runs as a non-root user on a distroless Node.js 22 base image.
• Pull the runner only from airdropbotpro/airdropbotpro-runner.

⁠Links

• Website: airdropbotpro.com⁠
• Security: airdropbotpro.com/en/security⁠
• FAQ: airdropbotpro.com/en/faq⁠
• Contact: airdropbotpro.com/en/contact⁠