ASCEND
Spinning up the arena…
Click to skip
ASCEND ASCENDASCEND · ROBINHOOD CHAIN
SEASON 0 · SPONSORED 1V1 PRESET LEAGUE · ROBINHOOD CHAIN

AGENT STRATEGYTRADING BATTLES

Same bankroll. One shared market. Best terminal ROI wins.

Two deterministic agents receive equal sponsored battle capital and trade temporary BTL units against the same on-chain AMM. Creators can choose a platform preset or an ownership-signed custom timing rule. The permanent AgentToken is their identity—not the asset being traded in battle.

round.phase → LIVE agent.reputation → 8214 score.source → BATTLEPOOL
What Is The Battle?

Agents compete to finish with more ETH than the field.

Season 1 is a sponsored 2–8 agent deterministic Battle Royale. It does not predict the external ETH price and it does not trade the contenders' ERC-20 AgentTokens.

The battlefield · BTL/ETH

BTL is a temporary internal accounting unit for one round. Every buy and sell moves the same constant-product price for both agents; BTL cannot leave BattlePool.

The equal start · 0.001 ETH

The shared platform runner funds the same fixed battle bankroll for each contender. The ETH used to launch or buy an AgentToken is completely separate.

The skill · timing and exposure

Presets enter at different moments, commit different portions of bankroll, and choose whether to exit before close or hold through final valuation.

The win · terminal bankroll ROI

Final score is terminal ETH value divided by starting bankroll. 10,000 bps is break-even; the highest immutable close snapshot is the winner.

Preset Agent Setup

Three steps from token to autonomous battles.

Deploy your agent with ETH, choose a platform preset or build a bounded custom rule, and the shared platform runner executes its on-chain battle actions.

1

Connect Wallet

Use MetaMask or Rabby on Robinhood Chain. Keep enough ETH for the factory launch fee and network gas; actual cost depends on current on-chain conditions.

2

Deploy Agent Token

Name it, choose Aggressive, Balanced, Defensive, or build a custom entry/exposure/exit rule, then deploy it through Factory V2. Custom rules retain an on-chain fallback preset.

3

Enter Sponsored Matchmaking

The shared runner rotates two to eight owner-enabled agents into each round, supplies every equal fixed bankroll, and executes a frozen preset or ownership-signed custom rule. Creator rewards and AgentToken funds remain creator-only.

Deploy Your First Agent Token
Round Lifecycle

Four phases. Contract-timed execution.

Every round opens a fresh temporary BTL/ETH market. Two contenders start with the same fixed bankroll, trade during LIVE, and finish with a return-on-bankroll score snapshotted by BattlePool.

01

Lobby

Enrollment

The oracle opens the next sequential BattlePool round and seeds neutral ETH liquidity. Agent runners watch the contract for the enrollment window. Open the arena →

02

MM-Only

30 seconds · Liquidity

The shared runner enrolls two rotated contenders with exactly 0.001 ETH each during the default 30-second window. Trading remains blocked until LIVE begins. How it works →

03

Live

Trading · 3 Minutes

Agents buy and sell temporary BTL units. Every action moves one shared on-chain price, so one strategy's timing changes the market faced by the opponent. Watch live →

04

Ended

Settlement

Trading stops and BattlePool calculates final position values and ROI scores. Agents claim position value separately; Settlement credits any funded RewardPool payout from the same canonical results. Past battles →

How You Win

Higher terminal bankroll earns the win.

BattlePool scores unspent ETH plus the closeout value of held BTL against the fixed starting bankroll: 10,000 bps means break-even. Trading PnL and separately funded RewardPool credits are different accounting flows.

Below break-even
<10,000 bps
Final position value is below the ETH allocated to the round.
trading loss
Break-even
10,000 bps
Final BattlePool position value matches the battle allocation before separate entry fees and gas.
flat ROI
Winner
Highest ROI score
Highest contract-calculated return this round. Takes the configured winner cut of the funded reward pool.
biggest share
Funded reward
Contract configured
Credited only when RewardPool holds ETH and Settlement successfully consumes the canonical round result.
claimable ETH
Why ASCEND

Trading positions, not house dice.

Every score is calculated from the agent's allocation and final BattlePool position. Settlement is permanently bound to those canonical arrays, so the oracle cannot add an entrant or reweight a score.

Configurable Rounds

BattlePool enforces MM and LIVE timestamps on-chain. The oracle schedules the next round after settlement using its configured delay.

No Leverage

No liquidation or negative balance inside BattlePool. Position exposure is capped at the ETH allocated to the round; entry fees and gas remain separate.

Explicit Preset Rules

Aggressive enters at 30%/uses 80%/exits at 65%; Balanced enters at 45%/uses 50%/exits at 82%; Defensive enters at 55%/uses 25%/holds to close.

On-Chain Execution

Round phases, allocations, swaps, final positions, scores, settlement, and claims are contract state or events on Robinhood Chain.

Legend
5M $ASCEND
One seat, ever.
×10.0
The Settlement Engine

New pool. Real trades. Canonical settlement.

The oracle only opens and closes each round. Agents trade for themselves, BattlePool calculates the scores, and Settlement verifies the exact canonical agent/score arrays before moving rewards.

01

Deploy with ETH. The creator pays the launch fee and initial curve buy; the shared runner separately funds battle allocation, entry fees, and gas.

02

Round opens. The oracle seeds neutral BattlePool liquidity and MM enrollment begins.

03

Agents trade temporary BTL. Wallet-signed buys and sells move the same constant-product price for both contenders.

04

Settlement. BattlePool calculates ROI scores and Settlement distributes the funded reward pool.

05

Next round. After settlement and the configured delay, an online oracle can open the next sequential round.

— NEXT ROUND · CONFIGURED ORACLE DELAY —
1%
Current fee on credited RewardPool payouts
Leverage inside BattlePool. Allocation, entry fee, and gas remain at risk.
Why It's Different

Verifiable. Continuous. Built in the open.

The UI reads AgentArena and BattlePool directly. Price lines come from Bought/Sold events, scores come from final positions, and production settlement is bound to BattlePool as its one-shot canonical result source.

DimensionPrediction MarketsASCEND
OutcomeBinary yes/no betsContinuous, score-proportional payout
Fairness mechanismTrust the resolverContract-calculated return on allocation
FrequencyHours to daysConfigurable contract-timed rounds
AgentYou make the betYour agent earns reputation every round
RiskOpen-ended or leveraged exposureBattle position capped at allocation; fees and gas separate
VerifiabilityOracle-dependent, opaqueTrades, positions, scores, and settlement checkable on-chain
How It Works

Your agent. Your rule. Verifiable execution.

Factory V2 deploys the token, stores its fallback preset, and grants a restricted shared runner permission to operate battles. Ownership-signed custom parameters are frozen per round; BattlePool and Settlement keep execution and accounting verifiable on-chain.

01 · Deploy Token

Create and register an AgentToken through Factory V2 using ETH for the launch fee and initial curve buy.

02 · Select Preset

Choose Aggressive, Balanced, or Defensive. The factory stores that selection for the shared runner.

03 · Shared Runner

The restricted runner discovers rounds, funds its positions, executes preset or bounded custom trades, and pays gas without custody of creator-owned balances.

04 · Trade & Claim

Claim BattlePool position value after close. Funded RewardPool credits, if any, are claimed separately and currently incur the contract's 1% payout fee.

Read the Whitepaper
Ready to compete?

Your agent. Your execution. Verifiable on-chain.

Share on X