SUBMISSION_CHECKLIST.md

Binance Agent OS Mini Hackathon — Track A submission checklist

Currentness checkpoint: 2026-09-07. Official announcement: https://www.binance.com/en/blog/community/8802181509900814931

Official X announcement: https://x.com/binance/status/2094810011557838988

Official survey: https://www.binance.com/en/survey/2913aa200aac462c89a737779393f3d4

Deadline stated by Binance: 2026-09-08 23:59 UTC (2026-09-08 20:59 BRT / UTC−03).

Technical package

  • Working hosted demo.
  • Read-only Binance market-data integration.
  • SKILL.md for an MCP-capable AI agent using Binance Agent OS Market Data.
  • Explicit safety boundary: no Account / Trade / Transfer required.
  • Evidence receipts.
  • Competing-hypothesis / falsification methodology.
  • Deterministic formulas documented.
  • API input allowlist and negative controls.
  • NO_TRADE_DECISION hard contract.
  • CSP and web hardening.
  • Automated release audit: 189 assertions + 35 rate-limit mutation steps = 224 checks PASS.
  • Source-failure/malformed-response mutation tests (MISSING_EVIDENCE != ZERO).
  • OAuth/CIMD/PKCE callback path implemented and locally falsified.
  • OAuth state TTL, replay rejection, concurrent single-consumer behavior and 500-row pending-state cap tested.
  • MCP 2026-07-28 stateless request metadata/headers tested with legacy fallback retained.
  • Synthetic MCP catalog proves Account/Trade/Transfer-like tools are excluded and tools/call is never automatic.
  • Runtime restrictions documented instead of hidden.
  • Public market-data path uses Binance's documented data-api.binance.vision surface; no API key required for these Spot reads.
  • Direct unauthenticated Agent OS transport probe classified: server/discover reaches server but is not implemented; tools/list returns OAuth 401. This proves the current MCP connection gate instead of assuming public data means anonymous tool-catalog access.
  • Real Binance Agent OS MCP connection proof in a supported MCP client, showing a Binance MCP Market Data tool returning BTCUSDT. Binance documents Market Data as public/no-auth at the capability level; keep Account, Trade and Transfer capabilities out of the PayAna demo.
  • Interactive screenshot/recording proof after final build — browser-automation providers currently require external credit/top-up; manual recording remains possible.

Official participation steps

These are external account actions and must be proven rather than inferred:

  • Confirm participant is eligible under the current Binance jurisdiction/account rules.
  • Follow @Binance on X.
  • Repost the official hackathon announcement.
  • Publish Track A reply or quote-repost containing the demo/video and GitHub link when applicable.
  • Complete the official Binance survey.
  • Preserve the resulting X post URL and survey success evidence in the project receipt log.

Suggested demo sequence

Target length: ~60–90 seconds.

  1. Problem (5–8s) — "Most market agents optimize for producing an answer. PayAna also tries to prove its own answer wrong."
  2. Agent OS connection (10s) — show the Binance MCP connected with Market Data-only permission, if authorization has been completed.
  3. Prompt (5s) — ask PayAna to audit BTCUSDT without trading.
  4. Evidence (15s) — show ticker, top-20 order book, 5m candles and source receipts.
  5. Neurônio/falsifier step (15s) — show winning hypothesis, opposite hypothesis, alternative explanation and observable falsifiers.
  6. Negative space (10s) — show missing funding/account/news/on-chain context instead of pretending it exists.
  7. Safety (8s) — show NO_TRADE_DECISION and MARKET_DATA_READ != TRADING_AUTH.
  8. Proof (10s) — show automated tests and hosted demo URL.

Suggested submission copy

Built PayAna — the Falsifier Agent for Binance Agent OS Track A. Instead of asking an agent only “what does the market say?”, PayAna also asks “what evidence would prove this reading wrong?” It uses Binance market data to build competing hypotheses, explicit falsifiers, missing-context checks and source receipts — with a read-only, no-trade safety boundary. Demo + code: [DEMO] [GITHUB] #Binance #AgentOS #BinanceMCP

Do not publish the placeholder version. Replace [DEMO] and [GITHUB] with final verified URLs first.

Evidence to preserve after submission

  • final Git commit / repository URL;
  • hosted demo URL;
  • final self-test output;
  • MCP Market Data authorization/connection proof if completed;
  • video/demo URL;
  • X submission URL;
  • survey completion proof;
  • UTC submission timestamp.