1. Every active competition runs simultaneously on Solana AND the chain returned by the backend (e.g.

   chainName=X Layer

   → activity runs on both X Layer and Solana). Solana is the hardcoded second chain on every activity.
2. Trades on either chain count toward the same competition standing. A user trading on Solana for an X-Layer-titled competition is participating, not bystanding. Likewise EVM trades count for a Solana-titled competition. (When backend later returns a multi-chain field listing all supported chains, drop this hardcoding.)

3. myRankInfo.userTotal = 0

   means the user has not yet hit the qualifying threshold or the backend metric pipeline has not picked up their trades yet — it does NOT mean the user's chain is unsupported. Never tell the user "your chain doesn't count" based on a

   userTotal=0

   observation.
4. The competition

   --wallet

   argument used in

   competition_rank

   is the chain-appropriate address: SOL for Solana-primary activities, EVM for EVM-primary activities. The address you pass is just a query lens — trades on the OTHER chain still count toward the same ranking.
5. The shape of point 1–4 may change in the future when backend exposes the full supported-chain list. Until then, NEVER answer "Does Solana count for this competition?" with anything other than YES.

chainName

## Output Language

Solana

• "list competitions / show available competitions" → Step 1 (table, optionally split by Active / Ended)
• "show details / show rules / show prize pool" → Step 2 (Basic info block + 4 reward sections, with hardcoded

  Solana, {chainName}

  and required participation / Skill copy)
• "register / join" → Step 3 (registration success fixed template + disclaimer)
• "trade for me" → Step 4 (delegate to okx-dex-swap)
• "leaderboard / ranking" → Step 5
• "claim reward" → Step 6 (use

  competition_claim

  MCP, atomic)
• "show registered wallet" → Additional Flows / Query Registered Wallet
• "export wallet" → Additional Flows / Wallet Export Guard

Read

../okx-agentic-wallet/_shared/preflight.md

. If missing, read

_shared/preflight.md

.

Internal-only IDs vs user-facing display. Internal numeric IDs (

activityId

,

chainIndex

,

accountId

) are returned in tool responses on purpose — they are needed to chain calls between tools (e.g. after

competition_join

, you may need to call

competition_detail

with the activity id to fill the success template). Keep them in the data layer; never render them in user-visible messages.

• ❌

  Agentic Trading Contest (#107)

• ❌

  #106 (agenticwallettest1)

• ❌ A column titled "ID" or "#"
• ❌ Any reference like "competition 107" or "id 107"

• ✅

  Agentic Trading Contest

• ✅ When disambiguating two activities with the same name, append

  chainName

  (e.g.

  Agentic Trading Contest (Solana)

  ), never the ID.

• ✅ Reading

  activityId

  from a

  competition_user_status

  /

  competition_join

  response and passing it to

  competition_detail

  to fetch the data needed by a fixed template.
• ✅ Any tool-to-tool chaining via numeric ids — as long as the final user-facing message omits them.

competition_claim

competition_join

activity_name

• Group rows by

  availableCompetitions[].status

  :

  3

  → Active table,

  4

  → Ended table.
• Name column ←

  name

• Chain column ← same hardcoding as Step 2: always include Solana plus the backend

  chainName

  .
  • If

    chainName

    is Solana → write just

    Solana

  • Otherwise → write

    Solana, {chainName}

    (e.g.

    Solana, XLayer

    )
  • Temporary until backend returns a full supported-chain list.
• Time column ←

  startTime

  ~

  endTime

  (human-readable, e.g.

  2025-04-01 ~ 2025-04-30

  )
• Total Prize Pool column ←

  rewards

  field (already a formatted string like

  50,000 USDC

  )
• Details column ←

  https://web3.okx.com/boost/trading-competition/<shortName>

  as a markdown link

• If only Active has entries:

  Which competition would you like to view in detail, or would you like to register directly?

• If only Ended has entries:

  Would you like to check your ranking or claim status for any of these?

• If both: combine —

  Which active competition would you like to register or view, or which ended competition would you like to check your ranking / claim?

• All filters returned 0 entries →

  No trading competitions available right now.

• status=0

  filter returned 0 entries →

  No active trading competitions at the moment.

• status=1

  filter returned 0 entries →

  No ended trading competitions yet.

• Chain line ← Solana first, then the backend

  chainName

  . Concretely:
  • If

    chainName

    already is Solana → write just

    Solana

  • Otherwise → write

    Solana, {chainName}

    (e.g.

    Solana, XLayer

    )
  • This is a temporary hardcoding because the backend currently returns only the primary chain. A future backend release will return the full supported-chain list as a separate field; remove this hardcoding then.

• {startTime}

  /

  {endTime}

  ← human-readable timestamps.

• {totalPrizePool}

  ← sum of all

  prizePoolDistribution[].totalReward

  plus

  rewardUnit

  (e.g.

  50,000 USDC

  ).

• {roiPoolAmount}

  ← totalReward of the realized-ROI tab.

• {pnlPoolAmount}

  ← totalReward of the realized-PnL tab.

• {participationPoolAmount}

  ← totalReward of the participation prize tab.

• {skillPoolAmount}

  ← totalReward of the Skill quality prize tab.

• {skillTopN}

  ← upper bound of the Skill tab's

  rules[].interval

  (e.g.

  "1-10"

  →

  10

  ).

• {skillPerCreatorReward}

  ← that rule entry's

  reward

  +

  rewardUnit

  (e.g.

  500 USDC

  ).

• {roiRankTable}

  /

  {pnlRankTable}

  ← markdown table built from the corresponding tab's

  rules[]

  . Format (English canonical; localize headers to user's language):

  | Rank | Reward |
  |------|--------|
  | <interval-formatted> | <reward-formatted> |
  | ...                  | ...                |
  | Total | <totalReward> {rewardUnit} |

  Interval / reward formatting per row:
  • Single rank (

    interval = "1"

    ) → Rank cell

    Rank 1

    , Reward cell

    <reward> <rewardUnit>

    (no

    each

    prefix)
  • Range (

    interval = "2-6"

    ) → Rank cell

    Ranks 2-6

    , Reward cell

    <reward> <rewardUnit> each

  • Always end with a totals row whose Reward cell is the tab's

    totalReward

    +

    rewardUnit

    .

• Title MUST be exactly

  Realized ROI Pool

  (or its faithful translation in the user's language). Do NOT substitute with

  PnL% Ranking Award

  /

  ROI Ranking Award

  / similar.
• Description MUST mention: ranking by realized ROI, high to low, during the competition period.
• Rank table MUST have headers

  Rank / Reward

  and end with a

  Total

  row.

• Title MUST be exactly

  Realized PnL Pool

  . Do NOT substitute with

  PnL Ranking Award

  .
• Description MUST mention: ranking by realized PnL, high to low.
• Rank table MUST follow the same format as Section 1.

• Title MUST be exactly

  Participation Reward

  .
• The description body MUST include all of these specific terms:

  • Agentic Wallet

  • cumulative trading volume threshold of

    $100

  • wallet total assets maintained at

    $100

    throughout
  • sharing the participation pool
  • asset snapshots to verify eligibility

• Title MUST be exactly

  Skill Quality Award

  .
• The description body MUST include all of these specific terms:
  • submission of Agent Skill via the activity page
  • examples of skill content (on-chain yield strategies, trade analysis, signal monitoring)
  • dual-rating mechanism of AI initial screening and human review

  • top {skillTopN} Skill creators ... each receive {skillPerCreatorReward}

Would you like me to register you for this competition?

competition_join

activity_name

chain_index

evm_wallet

sol_wallet

onchainos competition join --activity-id <id> --evm-wallet <evm_addr> --sol-wallet <sol_addr> --chain-index <chain_id>

chainIndex

competition_detail

chainIndex

not logged in — please run: onchainos wallet login

Please run

onchainos wallet login <your_email>

in your terminal to log in (it cannot be done from inside this conversation), then ask me to register again.

Your current wallet account [accountName] is already registered for [activityName]. No need to register again. Would you like me to walk you through the rules in detail, or start trading directly?

• [accountName]

  ←

  accountName

  of the currently selected account (read from

  wallet_store

  /

  wallet status

  , e.g.

  Account 1

  )

• [activityName]

  ←

  activityName

  from the prior

  competition_user_status

  /

  competition_list

  response

competition_join

code=11016 Participation limit reached

Registration failed. Your wallet account [registeredAccountName] is already registered. You cannot register again. Please switch to your registered account to trade.

• [registeredAccountName]

  ← name of the OTHER account in the same login that holds the registration. To find it, iterate every account from

  wallet_store

  other than the current one and call

  competition_user_status

  for the activity, picking the one whose

  joinStatus=1

  . If no account is found (rare race), fall back to a generic phrase like

  another of your wallet accounts is already registered

  and ask the user to check

  onchainos wallet status

  themselves.

Registered successfully! This competition runs simultaneously on {chainName} and Solana, with a total prize pool of {totalPrizePool}. The trading contest ranks players by both PnL% and realized PnL, with additional Participation and Skill Quality Awards. Would you like me to walk you through the detailed rules, or help you initiate a trade on {chainName} or Solana?

[Disclaimer: Digital asset trading involves risk. Prices can be highly volatile. Please understand the risks fully and do your own research before trading.]

• {chainName}

  ← backend

  chainName

  from

  competition_detail

  (e.g.

  XLayer

  ). Special case: if backend

  chainName

  is already Solana, the activity is single-chain — collapse the sentence to

  This competition runs on Solana

  and the trailing question to

  Would you like me to walk you through the detailed rules, or help you initiate a trade on Solana?

  . The disclaimer line still appears at the end either way.

• {totalPrizePool}

  ← total reward pool (sum of all

  prizePoolDistribution[].totalReward

  +

  rewardUnit

  , e.g.

  500 DJT

  ).

region

not available in your region

Registration failed: service is not available in your region. Please switch to a supported region and try again.

Operation failed. Please contact customer support.

1. Resolve the CA via the

   token_search

   MCP tool (CLI:

   onchainos token search

   ).
2. Confirm with user before proceeding:

   Just to confirm, the CA for token "{tokenSymbol}" is "{contractAddress}". Is that correct?

3. Wait for user to confirm. Only proceed after explicit "yes".
4. Then follow Case B below.

1. Execute swap via the

   swap_swap

   MCP tool (CLI:

   onchainos swap swap

   ); see the

   okx-dex-swap

   skill for parameters.
2. Report: "Done — your trade has been submitted." + tx hash.

Note: do NOT pre-empt the swap with an extra "token prices are volatile, do you accept the risk?" prompt. The user already requested the trade — additional friction is unwanted. Per-token risk metadata (e.g. honeypot / extreme volatility flags) belongs to

okx-security

and only fires when actually flagged.

• Single-trade min $1 (orders below $1 are not counted)
• Token pairs must match competition rules from

  detail

  response

onchainos competition user-status --evm-wallet <evm_addr> --sol-wallet <sol_addr>                       # all activities
onchainos competition user-status --activity-id <id> --evm-wallet <evm_addr> --sol-wallet <sol_addr>   # single

• If

  rewardStatus=1

  (won, not claimed): proactively ask "You have won a reward. Would you like me to claim it for you?"
• If

  rewardStatus=3

  (expired): "Your reward has expired and can no longer be claimed."

1. Call

   competition_detail

   for the activity and enumerate

   tabConfigs[].rankFieldConfig[].sortValueMap.descend

   — this is the full set of leaderboards the activity exposes.
2. Call

   competition_rank

   ONCE PER

   sort_type

   (one HTTP call per leaderboard) so you have data for every leaderboard.
3. Render ALL of them in the response — one section per leaderboard. Do NOT silently default to a single leaderboard (e.g. only

   sort_type=1

   ) when the activity has more than one.

tabConfigs[].rankFieldConfig[]

• title

  — display name (e.g.

  PnL%

  ,

  PnL

  )

• key

  — internal sort field (e.g.

  pnl

  ,

  realizedProfit

  )

• sortValueMap.descend

  — the numeric value to pass as

  --sort-type

onchainos competition rank --activity-id <id> --wallet <addr> --sort-type <descend> --limit 20

title

userTotal

format

PnL% leaderboard — pool 200 DJT Rank 1, Agentic....sMWP, PnL% +0.17%, estimated reward 100 DJT Rank 2, Agentic....gweD, PnL% +0.03%, estimated reward 20 DJT

PnL leaderboard — pool 200 DJT Rank 1, Agentic....sMWP, PnL $0.1885, estimated reward 100 DJT Rank 2, Agentic....gweD, PnL $0.0006, estimated reward 20 DJT

1. Call

   competition_detail

   → enumerate

   tabConfigs[].rankFieldConfig[].sortValueMap.descend

   to get the full set of

   sort_type

   values for this activity.
2. For EACH

   sort_type

   , call

   competition_rank --sort-type <descend>

   and capture

   myRankInfo

   plus the leaderboard's threshold (lowest

   userTotal

   in

   allRankInfos

   ).
3. Classify the result:
   • CASE 1 — user has

     currentRank > 0

     on every leaderboard
   • CASE 2 — user has

     currentRank > 0

     on at least one but not all
   • CASE 3 — user has no

     currentRank > 0

     on any leaderboard
4. Output the matching fixed template, rendered in the user's language (English canonical below; localize for Chinese / other-language users).

• {pnlRank}

  ←

  myRankInfo.currentRank

  of the PnL leaderboard (sort_type 7)

• {pnlReward}

  ←

  myRankInfo.expectedRewards

  of the PnL leaderboard

• {roiRank}

  ←

  myRankInfo.currentRank

  of the PnL% leaderboard (sort_type 1)

• {roiReward}

  ←

  myRankInfo.expectedRewards

  of the PnL% leaderboard

• {rewardUnit}

  ←

  myRankInfo.rewardUnit

  (e.g.

  DJT

  ); per-leaderboard if they ever differ

• {totalReward}

  ←

  pnlReward + roiReward

  (numeric sum, same unit)

• {currentRoi}

  ← user's PnL% score from

  myRankInfo.userTotal

  of the PnL% board (or 0 if backend returned null)

• {currentPnl}

  ← user's PnL score from

  myRankInfo.userTotal

  of the PnL board

• {minRoi}

  ← lowest qualifying PnL% — last entry's

  userTotal

  in the PnL% board's

  allRankInfos[]

• {minPnl}

  ← lowest qualifying PnL — last entry's

  userTotal

  in the PnL board's

  allRankInfos[]

tabConfigs[]

expectedRewards

format

1

2

3

Result shape (both paths):
```json
{
  "rewardAmount": "460",
  "rewardUnit": "PYBOBO",
  "totalEntries": 1,
  "succeeded": [{"contractAddress": "...", "chain": "501", "txHash": "...", "orderId": "..."}],
  "failed": []
}

• All succeeded (

  failed: []

  ): "Claimed {rewardAmount} {rewardUnit}, tx hash: {txHash}"
• Partial success (some

  failed

  ): list each succeeded txHash, then list the failed entries with their

  error

  , then append the fixed failure-suggestion block (template below). Do NOT re-run claim blindly — succeeded entries already landed; another call will hit the "reward already claimed" guard.
• All failed: the tool returns an error, not this shape — surface the error message verbatim, then append the fixed failure-suggestion block.

rewardStatus

1. Call

   competition_user_status

   (MCP) — addresses auto-resolve from the active account; no

   wallet_status

   needed. CLI equivalent:

   onchainos competition user-status --evm-wallet <evm_addr> --sol-wallet <sol_addr>

   (omit

   --activity-id

   to query all activities).
2. Find entries where

   joinStatus=1

3. For each matched entry, present: competition name (

   activityName

   ) + chain (

   chainName

   ) + masked address (first4...last4). Use chain to determine which address was used (EVM or SOL).

Your Account 1 is registered for XXX Trading Competition. Registered address: Solana address DeEV...Fbx.

Your Account 1 is registered for the following trading competitions:

• XXX Trading Competition (Solana): DeEV...Fbx
• YYY Trading Competition (XLayer): 0x1234...abcd

joinStatus=1

You are not currently registered for any trading competition.

1. Call

   competition_user_status

   (MCP) — addresses auto-resolved. CLI equivalent:

   onchainos competition user-status --evm-wallet <evm_addr> --sol-wallet <sol_addr>

   .
2. If any

   joinStatus=1

   :

   Your wallet is registered for an Agentic Wallet trading competition. Exporting the wallet will forfeit your eligibility for this competition. Please confirm whether you want to proceed with the export.

3. Only proceed with export if the user explicitly confirms.