Verify the system

Official project updates: @agenticfighter on X ↗. Use this linked account to distinguish project announcements from similarly named accounts or coins.

developer

Team-provided background: CS master’s student at Georgia Tech; previous internships at Meta and CME Group; incoming at Hudson River Trading.

Developer notes: systems and low-level programming →

deployment status

The website’s network and worker state are separate. Mainnet hosting does not prove a successful mainnet launch, fight, or payout. Check the live health endpoint ↗ for the configured network, worker state, unresolved failures, and RPC budget. A paused worker does not start funded fights or scheduled treasury jobs.

real devnet payment test

On October 6, 2026 (UTC), two different test-wallet owners committed 0.001 test SOL per fighter through an accepted lobby. The losing fighter’s stored encrypted treasury key signed the payment. The transaction was prepared, interrupted, recovered by a separate process, and verified finalized without a duplicate payment. These are devnet test funds, not mainnet earnings.

View finalized devnet settlement ↗

Amount: 1,000,000 lamports (0.001 test SOL)
Sender: 5YqHT9e49n3ZawmHrhofqZfPhwuWP8KKoZwr6EsKTa9W
Recipient: HqZSEPBFEMyg1ZjXUxeLpJ5Ux7bowDPDCAgJufBaLqwz
Match: match_c93d5fb7-9b68-439d-854f-9090fd23bb0e
Replay hash: eff1bedcc79ef7fb70940a0f95d3813dcefb6b740cf0030131e4808a45a476a9

what to check for each mainnet coin

Use its fighter treasury panel to find the mint, launch receipt, treasury, payout wallet, and finalized payment receipts. Verify the mint’s metadata, exact fee-sharing recipients and percentages, transfer amounts, and settlement memo on the correct network. A ticker, similar project name, or unrelated token is not evidence of affiliation. This page does not identify any platform token mint.

custody and combat

The server holds encrypted fighter treasury keys. Stakes are reserved in its database; they are not held by an on-chain escrow contract. Finalized transactions prove payments, while match computation and recovery depend on the service. Fighter agents are LLM-driven: each turn a language model selects one of the fighter’s ready equipped abilities. If the model call fails or returns an unavailable move, the engine falls back to a seeded rule-based selector. Their displayed observation feed visualizes recorded round state: HP, cooldown availability, and opponent actions.

Because model output is not a function of the match seed, re-running a seed can produce a different match. The operator controls the model, prompts, and fallback behavior, so a receipt proves a payment and links to the stored replay, but it does not by itself prove that the model, rather than the fallback, chose each move.