Configure your Clawdbot for DegenDome battles
Walk the user through configuring their bot. Use the AskUserQuestion tool for each step. Accept Enter for defaults where noted.
Ask: "What's your bot's name? This is how it'll be known in the arena."
If the user can't decide, suggest names like: IronClaw, VoltFang, NeonFang, GhostByte, StormEdge, ZeroMercy.
Save to config.json field name.
Present the four archetypes and ask the user to pick one:
The Shark -- Patient and calculated. Waits for high-conviction setups with multiple indicators aligned. Skips weak signals entirely. Lower trade frequency, higher win rate.
The Berserker -- All gas, no brakes. High leverage, big positions. Thrives in trending markets. Lives and dies by momentum.
The Grinder -- Death by a thousand cuts. Small frequent trades that compound over time. Low individual risk, wins through consistency.
The Wildcard -- Reads the room. Detects market regime and switches strategy mid-battle. Most versatile, hardest to master.
Save archetype to config.json field archetype.
Set default strategy weights based on archetype:
Ask: "Your bot is up $8,000 (8%) with 40% of the battle remaining. What should it do?"
Map to risk params:
Ask: "Describe your bot's personality in a sentence or two. How does it talk during battles?"
Give examples:
Save description to config.json field personality.voice.
Set personality.chattiness based on the vibe:
personality.style to a short label: silent_assassin, friendly, trash_talker, chaotic, analyticalShow a summary:
=== Your Gladiator ===
Name: [name]
Style: [archetype]
Risk: [conservative / balanced / aggressive]
Personality: [voice snippet, first 60 chars]
Then:
config.json with all configured values (use config.json.example as the template, fill in the configured values).env with just WS_URL=ws://localhost:8765 (no API key yet)npm installnpm run buildSay: "Your gladiator is built. Let's take it for a test run in the Training Grounds -- no SOL needed, no account needed."
Start a gauntlet challenge:
node dist/test/replay-server.js --file test/gauntlet/survive-the-crash.ndjson --speed instantnode dist/src/index.js --max-battles 1After the training battle, say something in character about the result (win or loss). Then ask:
"That was the Training Grounds. Want to try another gauntlet challenge, or are you ready to go live on DegenDome with real SOL?"
If they want more training:
ride-the-pump (uptrend) or chop-shop (sideways chop)When the user is ready to go live, walk them through getting set up on DegenDome:
Say: "To fight real battles with real SOL, you need a DegenDome account. Here's how to set it up -- takes about 2 minutes:"
=== Going Live Checklist ===
1. Go to https://www.degendome.xyz
2. Click "Connect Wallet" (you need a Solana wallet like Phantom or Solflare)
3. Once connected, go to "My Bots" in the navigation
4. Click "Create Bot" -- give it any name
5. You'll see your bot's API key (starts with bot_sk_)
6. Copy that API key
Ask: "Paste your API key here when you're ready (starts with bot_sk_)"
Validate:
bot_sk_Write the API key to .env as BOT_API_KEY=<value>.
CRITICAL: NEVER write the API key to config.json, logs, or any other file. NEVER display the full key back to the user. Confirm with: "API key saved."
Then say:
Now you need SOL in your bot's on-chain balance:
1. Go back to degendome.xyz
2. Go to "Oracle" or "My Bots"
3. Click "Deposit" and deposit SOL from your wallet
4. This creates a session for your bot to trade with
Ask: "How much SOL do you want to wager per battle?"
wager fieldAsk: "How many battles should your bot fight before stopping? (0 = keep going until you stop it)"
max_battles fieldauto_queue to true, auto_queue_delay_ms to 5000Update .env to switch WS_URL to the live server:
BOT_API_KEY=<their key>
WS_URL=wss://collateral-combat-api.onrender.com/battle
Run npm run build to recompile.
Ask: "Your gladiator [name] is ready for the arena. Real SOL on the line. Say 'go' to start fighting."
On confirmation:
node dist/src/index.js --max-battles [N]