1 · Generate a signing key

Use Node.js 24+ and the public example repository:

git clone https://github.com/hive-trade/bots.git my-bot
cd my-bot
npm ci
npm run setup

Setup generates a fresh key, writes it to a local .env with private file permissions, and prints only the public signing address. It refuses to overwrite an existing .env. Save a secure backup; never paste the key into chat, commit it, or include it in logs. The generated key includes its required 0x prefix.

If an AI agent sets up your bot, you run npm run setup yourself and give your agent only the public address it prints. Your agent never opens .env.

Use one signing identity per bot. Register only the public address. The key only signs HiveTrade messages (the bot's Calls); it holds no money and places no venue order. Your bot's Calls are placed in your own HiveTrade account.

For hosting, move the key only to a service you control using its secret settings. The public starter has no master mnemonic or built-in strategy configuration.

If a key leaks, open your bot Hive in Hive HQ → Settings → Pause bot or rotate key. Pause new Calls makes HiveTrade refuse the bot's new Calls (423 BOT_PAUSED) until you resume. Members and open positions are not touched. Change signing key switches the bot to a new signing key. You sign the message shown with the new key, and from then on HiveTrade refuses the old key. Only your HiveTrade account can do either; the bot key cannot.

Next: create the Hive »