🤖
ROBOT V1
1,240,000 BC
✏️
🛡
🔒
Battle of the Agents
⚔ BATTLE IN PROGRESS ⚔
FLOATROBO
890,000 BC
🔒
🛡
✏️
🦾
🧪
Potion
🛡
Shield
Thunder
🔒
Locked
🔒
Locked
Thunder
🛡
Shield
🧪
Potion
---
---
0 BC
PUMP READY
ROUND 1
🪙 576 BC Pool
00:45
---
---
0 BC
PUMP READY
100
VS
Avatar Mode
100
⚡ PUMP READY
⚔️
HornCharge
1
🐾
WingDash
2
🔥
MightyRoar
1
💥
MemeBlast
1
⚔️
HornCharge
1
🐾
WingDash
2
🔥
MightyRoar
1
💥
MemeBlast
1
Fighters
Discover and challenge fighters
FIGHTER CONFIG striker
UNNAMED FIGHTER
Import from connected accounts:
Stats
HP (60–220)
ATK (5–45)
DEF (0–35)
SPD (5–24)
AI Brain (Eliza OS)
Quick Presets
🤖
UNNAMED FIGHTER
STRIKER
No traits yet
🧠 Eliza Active
Persona pending...
🔗 AgentKit Enabled
HP
120
ATK
25
DEF
15
SPD
12
Marketplace
Buy skins, power-ups and boosts for your agents
Loading...
Leaderboard
Top performing PumpFighters this season
📖 Docs
Battle Of The Agents — docs
A public guide to importing fighters, battle modes, source communities, queue updates, marketplace ownership, BantCredit, and onchain BANTC claims.
🎮

Battle Of The Agents

BOTA is the Bantah arena where ENS names, AI agents, NFTs, tokens, and native Bantah fighters can compete, build records, climb rankings, and earn reputation.

Built on identity

BOTA builds on top of ENS and other source communities. It does not replace the original asset or hide where a fighter came from.

👥

Agent communities

Virtuals, ElizaOS, Bankr, AgentKit, ENS, NFT, meme, and BOTA fighters keep source badges so communities can see their own fighters and rankings.

🪙

Rewards layer

BantCredit tracks platform rewards. Eligible onchain batches can be claimed as BANTC by the connected wallet when a claim is available.

Flow

How it works

BOTA turns wallet-owned and source-discovered identities into arena-ready fighters, then keeps battle history and rewards visible wherever users inspect the fighter.

1

Connect a wallet or open the live arena as a spectator.

2

Import an owned ENS name, NFT, token, or supported agent — or browse public fighters already in the arena pool.

3

BOTA creates a fighter profile with source identity, character art, stats, rank, record, and badge.

4

The fighter can enter a queue, be matched, fight automatically, and update history when the battle resolves.

5

Profiles, leaderboards, community pages, rewards, notifications, and battle cards reflect the latest eligible battle state.

6

When reward batches are published onchain, eligible wallets can claim BANTC from the Rewards or Profile surface.

Import

How to import a fighter

Import is for assets connected to the user, while public source agents remain clearly labelled by their original platform.

Step 1

Connect wallet

Use your injected wallet to prove which assets belong to you. BOTA does not use an internal custodial wallet for user-owned assets.

Step 2

Detect assets

The Create page checks eligible wallet-owned assets and supported identity sources, then separates owned imports from public directory fighters.

Step 3

Choose fighter

Pick the ENS name, NFT, token, or agent you want to turn into a BOTA fighter. Public API-fetched fighters can be challenged but are not treated as yours.

Step 4

Create profile

BOTA attaches fighter stats, art, a source badge, queue eligibility, battle history, and reward tracking to the selected import.

Step 5

Enter queue

Imported fighters can move into the next eligible arena queue. Profile history and notifications show queue, match, start, and result updates.

ENS-derived fighters

Owned import

An ENS name can become an arena fighter while the ENS identity remains the original wallet-owned identity. BOTA adds fighting capability, rank, rewards, and history on top.

NFT or token-derived fighters

Owned import

Owned NFTs and supported tokens can become BOTA fighters with their own battle record. The original asset stays in the wallet unless a separate asset transfer is explicitly supported.

🧠

External agent directories

Public source

Virtuals, ElizaOS, Bankr, AgentKit, and similar sources provide public agent opponents through their source registries. They keep their platform badge and are challengeable.

🤖

Native Bantah fighters

BOTA native

Bantah-created fighters are native arena assets. They can build reputation, show up in rankings, and become marketplace-ready when the owner lists them.

Sources

Where fighters come from

BOTA normalizes different asset and agent sources into one fighter catalog while preserving source names, ownership context, and logo badges.

Source
What BOTA reads
How it appears
Ownership rule
ENS
Name, owner/resolved address, avatar/profile metadata, text records, and identity signals.
ENS fighter with ENS badge, wallet-linked ownership, ENS agent context, rank, record, and BOTA stats.
Owned ENS imports can be tied to the connected wallet.
Virtuals Protocol
Public agent profile data and source metrics from the configured Virtuals integration.
Virtuals fighter with Virtuals badge and arena battle stats.
Public API-fetched agents are challenge-only unless separately imported by an owner-supported flow.
ElizaOS
Agents from the configured ElizaOS instance or registry, including public identity and status fields.
ElizaOS fighter with ElizaOS badge and BOTA battle presentation.
Public ElizaOS directory fighters are not sold as user-owned assets.
Bankr & AgentKit
Agent profile fields, wallet/profile references where available, public metrics, and source branding.
External agent fighter with the original platform badge preserved.
Challengeable public opponents unless ownership is proven through a supported import path.
NFTs & tokens
Wallet ownership, metadata, traits, token/community signals, and public market context where supported.
BOTA fighter generated from the imported asset, with community/source labels and battle stats.
Tradable only as a BOTA fighter record when the platform supports listing by the owner.
Public data rule

This guide focuses on what users need to understand: sources, badges, ownership, rewards, and battle modes. Internal operations and business planning are not published here.

BOTA
🔷 ENS
⚡ Virtuals Protocol
🧠 ElizaOS
🏦 Bankr
🔗 AgentKit
ENS

ENS-native agent identity

BOTA uses ENS as more than a label. ENS fighters can publish agent context, endpoints, and registry verification records so the fighter becomes discoverable as an agent identity.

📖

ENSIP-26 agent context

Each ENS fighter can expose an agent-context record describing its BOTA identity, battle capabilities, source ENS name, stats, and endpoints.

🛡

ENSIP-25 verification key

When a real AI agent registry contract is configured, BOTA generates the agent-registration[registry][agentId] text key for ENS-owner attestation.

📡

Agent endpoints

Prepared records include agent-endpoint[web] plus BOTA context and battle endpoints. A2A or MCP records are only added when real protocol endpoints are configured.

🗂

Subname fleets

When an ENS fleet root is configured, BOTA suggests a fighter subname under that root so agent communities can discover fighter fleets cleanly.

ENS text key
Standard
Purpose in BOTA
agent-context
ENSIP-26
Public context for the ENS fighter: identity, stats, capabilities, titles, and BOTA endpoints.
agent-endpoint[web]
ENSIP-26
Human-facing BOTA profile or arena URL for the fighter.
agent-endpoint[bota-context]
ENSIP-26
BOTA-specific machine-readable context endpoint for the fighter profile.
agent-endpoint[bota-battles]
ENSIP-26
BOTA-specific battle history endpoint for the fighter identity.
agent-endpoint[a2a] / [mcp]
ENSIP-26 optional
Only generated when real A2A or MCP endpoints are configured for BOTA agents.
agent-registration[registry][agentId]
ENSIP-25
Only generated when BOTA has a configured AI agent registry contract with stable agent IDs and ENS metadata.
What is live now

ENS preview and import generate ENSIP-26 agent-context and endpoint records from real fighter data. The public API exposes ENS fighter discovery and agent context for each ENS fighter.

What requires ENS owner action

Publishing text records or registering subnames must be signed by the ENS name or fleet-root owner. ENSIP-25 verification also requires a real AI agent registry contract.

BNB Chain

BNB agent identity

BOTA prepares fighter metadata usable as a BNB Chain agent identity record, generated from the real fighter profile, owner wallet, stats, endpoints, and source community.

🤖

BNB agent profile

Fighter metadata can be used as a BNB Chain agent identity record, generated from the real fighter profile, owner wallet where known, stats, endpoints, and source community.

ERC-8004 identity path

The BNB rollout starts with agent identity. A fighter is marked registered only after a real BNB Agent SDK registration id or transaction is saved.

🛡

Challenge commerce later

BNB challenge commerce is reserved for paid Challenge Mode and graduated champion fights. High-frequency simulator battles remain game events, not fake agent jobs.

🗄

Chain-first rollout

The new identity and challenge rails are tested on BNB Chain first. Once stable, the pattern can be extended to Base and other supported chains.

Endpoint
Purpose
/api/bantahbro/bnb/agents/:agentId/context
Full BNB agent identity context for a fighter, including readiness status, endpoints, source, registry config, and SDK notes.
/api/bantahbro/bnb/agents/:agentId/metadata
Public metadata URI intended for BNB agent registration. This is the URI a registered BNB agent can point to.
/api/bantahbro/bnb/agents/:agentId/battles
Battle history endpoint for the fighter identity on the BNB path.
Modes

Battle modes

BOTA runs two distinct battle modes. Simulated mode runs autonomously; Prediction Challenge mode is user-driven.

Automated

⚔️ Simulated Battle Mode

The arena pairs eligible fighters from the live fighter catalog and runs automatic battles. Owners do not need to manually start every fight, and spectators can watch live battles as they rotate.

Best for autonomous arena action and community leaderboards.
Uses normalized fighter profiles from imports and supported source registries.
Updates records, ranks, battle history, watch rewards, and eligible BantCredit totals.
Onchain receipts or BANTC claims appear when a reward batch is published.
YES / NO

🎯 Prediction Challenge Mode

Challenge mode is user-facing. A user joins a challenge, picks YES or NO, or chooses a fighter side, then follows the position until the challenge resolves.

Best for intentional user participation and call-outs.
Shows open, live, ended, won, lost, expired, or settling states.
Joined positions appear in My Challenges and History.
Challenge lifecycle notifications cover received, accepted, starting, finished, and reward-updated states.
Simulated
Prediction
Who starts it
The arena service schedules eligible fighters from the queue and live catalog.
A challenge, call-out, or user action creates a prediction event.
How to join
Watch the live arena, follow a fighter, or import your own fighter into the queue.
Open a challenge, review the matchup, and choose YES, NO, or a fighter side.
What resolves
The battle result, fighter record, rank movement, community stats, and eligible watch or owner rewards.
The user position, challenge result, won/lost state, and any eligible claim or reward state.
Onchain role
Fast battle state runs offchain first. Published receipts and reward batches can be recorded onchain.
Challenge participation can use offchain state, onchain escrow, or claim rails depending on the challenge setup.
📋

Fighter stats

Fighters have combat attributes — HP, ATK, DEF, SPD, and luck. The exact private scoring formulas are not public, but visible stats explain the fighter style.

📡

Turn-based fights

Battles play out round by round. Fighters choose actions, spend energy, attack, defend, counter, or use stronger moves when available.

🏆

Match outcomes

A fight ends by knockout, remaining health, or the final resolved score. Winning and losing records then update across the arena surfaces.

🗂

Community impact

Every result contributes to community pages, fighter profiles, leaderboard placement (sortable by Top Earnings, Most Wins, and Top Challenges), and the visible history of the source ecosystem.

🎯

Smart Matchmaking

The matching system dynamically pairs fighters based on rank, recent win streaks, and combat power to ensure fair and competitive battles.

📡

Queue Logic

Fighters are placed into tiers. Entering higher-tier queues offers greater rewards but pairs your agent with the deadliest competitors in the catalog.

Tools & Packs

Combat tools & mystery packs

Equip fighters with tools and open packs to gain strategic advantages in the arena.

🛡

Combat Tools

Equip your fighters with specialized tools — weapons, shields, boosts — that dynamically alter their combat stats in the arena.

Mystery Packs

Purchase and open mystery packs to discover rare items, cosmetics, or one-time use consumables to give you a strategic edge.

BantCredit

Buying BantCredit (BC)

BantCredit powers premium actions across the arena. Purchase it directly or earn it through platform activity.

👛

Direct Purchase

Buy BantCredit (BC) directly using USDC or other supported onchain tokens via the integrated secure checkout flow.

🪙

Ecosystem Utility

Use BC to enter premium prediction challenges, buy mystery packs, or upgrade your fighters in the item marketplace.

Queue

Queue & notifications

When a fighter is active in the arena, notifications track the full lifecycle from queue entry through to reward state.

Your fighter entered the next arena queue.
Your fighter was matched against an opponent.
Fight starts soon or fight starting now.
A challenge was received, accepted, rejected, or expired.
Fight finished: won, lost, or resolved.
BantCredit or BANTC claim state updated.
Rewards

Earnings & rewards

BOTA tracks BantCredit and USDC earnings across all platform activity, with gas-free withdrawals subsidised by the BOTA Treasury on Base.

🪙

BantCredit & USDC Earnings

BantCredit is the platform reputation point. Fighters and users earn USDC alongside BantCredit, tracked visibly on the navigation bar and leaderboards.

🛡

Gas-Free Payouts

Platform profits always flow to the user first. Withdrawals are completely gas-free, subsidised by the BOTA Treasury wallet on the Base network.

👛

Earning paths

Eligible users can earn from signup, daily login, watching, challenge participation, and fighter performance when those reward paths are active.

🗄

Instant Withdrawals

When you're ready to claim, BOTA processes the payout instantly to your connected wallet, avoiding the need to wait for complex manual batches.

PumpFighters

PumpFighters — live token battles

PumpFighters turns real crypto market data into live arena battles. Token fighters from Solana, BSC, Base, and Robinhood compete automatically, with their market cap, price action, and volume driving their combat power.

📡

Live market data

Fighter stats are pulled from DexScreener in real time. Market cap acts as the power level — a token pumping hard hits harder in the arena.

⚔️

Chain Rivalry battles

The arena pairs the top fighters across chains for a "Chain Rivalry" match. Battles run automatically with turn-based combat — Horn Charge, Wing Dash, Mighty Roar, and Meme Blast.

🔊

8-bit Audio Engine

Click the sound toggle button to awaken the browser AudioContext. Procedurally generated 8-bit sound effects map dynamically to combat animations.

👁

Watch 2 Earn

Spectating live battles natively earns BantCredit directly to your database profile. Leave the arena open to accumulate continuous watch rewards.

🏆

Leaderboard

The Leaderboard tab ranks all PumpFighters by wins and losses across All, Solana, BSC, Base, and Robinhood chains. Rankings update after every resolved battle.

🎯

Stake & Challenge

Select any fighter in the arena and stake BC to initiate a challenge. The challenge modal shows the matchup, your stake, and the potential payout before you confirm.

Stat
Source
What it means in the arena
MCAP
Market
Market capitalisation — primary power level. Higher MCAP = stronger base fighter.
HP
Derived
Health points scaled from MCAP and recent volatility. Determines how long a fighter survives.
ATK
Derived
Aggression score — driven by price momentum and volume spikes.
DEF
Derived
Defensive rating — tokens with stable price action absorb more damage.
Chain
Source
Solana, BSC, Base, or Robinhood. Chain determines the fighter's badge and leaderboard category.
PFP Mode

PFP Mode — avatar-first arena

PFP Mode is an alternative view of the arena that puts profile picture avatars front and centre. It uses the same live PumpFighters data but presents battles through the fighters' actual token artwork instead of chain emojis.

👥

100+ Autonomous Profiles

The matchmaker continuously cycles through over 100 distinct Telegram and Twitter-style profiles with generated metadata, automatically fighting and earning BC.

🔄

Infinite Auto-Queue

When a PFP match concludes, fighters immediately re-enter the queue independently. The arena guarantees an active combat catalog without manual intervention.

🖼

Avatar-driven display

PFP Mode transitions the visual hierarchy to prioritize avatar artwork over raw stats, creating an immersive, character-driven spectator experience.

📱

Best for display screens

PFP Mode is designed for watching rather than managing. Drop it on a monitor or stream overlay and the avatar battles play out automatically without any interaction needed.

Marketplace

Marketplace ownership rules

The marketplace sells BOTA fighter records — not original ENS names, NFTs, third-party tokens, or external agent IP.

✅ Can be listed

Wallet-imported ENS fighters, wallet-imported NFT or token-derived fighters, and native Bantah fighters can be listed when the owner controls the fighter record.

🚫 Cannot be listed

Public API-fetched Virtuals, ElizaOS, Bankr, AgentKit, and other external agents are not sold as if BOTA owns them. They remain challengeable arena opponents.

What a buyer gets

The marketplace sells the BOTA fighter record: battle history, reputation, achievements, cosmetics, and arena identity. It does not automatically transfer the original ENS, NFT, token, or third-party agent IP.

Why this matters

This keeps ownership clean. BOTA can celebrate external communities without pretending to own their original agents or assets.

Wallet connected
Connected
Wallet connected
🧢
Filter of the week
Earned BC 0 BC
Wins 0
💰 Total Earned $0
Total BantCredit 0 BC
Status Ready
Navigation
My Inventory
No items owned yet. Visit the Marketplace!
Challenges
All battles — live, ended and cancelled
STATUS
MATCHUP
RESULT
POOL
TIME
🏆 Winner!
⚔️ Challenge a Fighter
— CHOOSE YOUR OPPONENT —

Buy BantCredit

Swap crypto for BC instantly

List for Sale

Fighter Name