KAON Public Alpha
Licensed Research Market
KAON remains the Ethereum-side asset. BION is the Base utility layer for licenses, task access, and frequent platform work: stake BION, complete reviewed research, and build public reputation backed by auditable reward accounting.
Licensed Work
Trial, Challenge, and research tasks make the value loop visible: selected specialists submit work and creators review it. Public reward evidence is recorded after review.
Public Reputation
Reputation, reward-ledger state, and task evidence are public so users can inspect who actually produces value. Prediction track records belong to Phase 2.
AI Market Tools
AI and market-data workflows support research decisions. They are informational tools, not financial advice or automated trading guarantees.
Why KAON should feel worth paying for
The sales point is not a token promise. It is an operations hub where AI research becomes licensed work, reviewed evidence, public reputation, and reward accounting users can inspect.
Pay for AI capacity when it saves research time: focused briefs, route readiness, watchlist monitoring, reusable artifacts, and task handoff.
Boundary: AI output is private research until saved, audited, or converted into a reviewed task.
Pay for bounded financial research work with acceptance criteria, reviewer notes, dispute handling, and reusable public outcomes.
Boundary: A task is credible only when reward rules, review criteria, and funding/accounting state are visible.
Stake BION when you want access to work, public reputation, task history, and reviewed reward accounting.
Boundary: License access is not passive yield and does not execute Ethereum payouts by itself.
AI turns market noise into reviewable work
Users get structured briefs, source freshness, evidence gaps, and task-ready drafts instead of another generic chat answer.
Proof: AI Workspace stores private thesis artifacts, task drafts, quota audit rows, and a prompt-to-output timeline.
Run AI WorkspaceStake BION for work access, not token inflation
A Base-side license creates task eligibility, tier context, labor power, reward weight, and an active-task lock.
Proof: License reads, task gating, and backend create/apply/publish checks all require an active non-locked license.
Check licenseThe core product is reviewed specialist labor
Creators pay for a concrete conclusion: validation, risk review, route check, data label, or alpha brief with acceptance rules.
Proof: Task lifecycle covers application, selection, submission, review, dispute, ledger, and payout-accounting states.
Browse tasksPublic proof separates earned, queued, and paid
The community can inspect what was done, who did it, why it was approved, and whether transaction evidence exists.
Proof: Activity, task proof map, specialist profiles, and transparency metrics expose metadata instead of hiding claims behind marketing copy.
Inspect proofRoute preview becomes a verification task
Users can describe a bridge/swap intent in chat, see parsed assumptions and route risks, then draft a route-check task.
Proof: Route cards show readiness, blockers, fees, route steps, alternatives, and preview-only copy.
Preview routeOperators get a real accounting control plane
Public Alpha can queue reviewed reward accounting, prepare payout manifests, attach transaction evidence when it exists, and monitor stale license locks.
Proof: Operations panel distinguishes global payout-batch preparation from per-user proof rows and never exposes admin keys.
Read runbookPublic Alpha proves the work loop first. KAON to BION migration, revenue pools, buyback/burn evidence, and legacy claims must be shown as evidence-backed only when those flows are live.
No launch claim without evidence
Run strict go/no-go against app.kaon.global with deployed route, auth, quota, Lab WS, LI.FI, market-data, and task lifecycle evidence.
Publish at least five real Trial/Challenge/Research tasks and verify they are visible on the public board.
Record a small USDC/USDT payout transaction and confirm user Activity, task detail, and Transparency show paid proof correctly.
Sync two licensed wallets from the target StakingLicense contract and prove assignment/completion/failure events update ledger state.
Finish snapshot, Merkle proofs, funding, deploy evidence, security review, and claim-event sync before enabling execution.