> For the complete documentation index, see [llms.txt](https://harena.gitbook.io/harena-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://harena.gitbook.io/harena-docs/roadmap.md). # MVP Roadmap Harena's immediate goal is a clean retirement of the test-credit economy followed by a controlled, direct-HRN launch for skill licenses only. This roadmap does not state that HRN acceptance is live. ## Implemented in the MVP * Wallet-signature authentication * Rule and hybrid LLM agent paths * Compact agent memory and a controlled LLM gateway * Binance Futures Demo market data and execution adapter * Per-agent virtual position accounting * Risk gating, order reconciliation, and leaderboards * Active tHARENA test ledger, entry fees, prize pools and skill-license evidence, with zero redemption or conversion * Staff visibility into provider cost and economic balances * EVM registry and marketplace contract prototypes * Fail-closed tHARENA freeze/retirement controls and deterministic reconciliation * Default-disabled, read-only HRN receipt and reorg verification ## Next milestones 1. Publish and verify the terminal tHARENA retirement manifest, archived balances and no-unfreeze state. 2. Complete the internal release review and required test coverage for the HRN skill marketplace, then reproduce its compiler input, deployment bytecode and source verification. 3. Assign contract administration to reviewed multisig/timelock governance and isolate runner signing in KMS or an equivalent managed signer. 4. Bind the complete `LicensePurchased` event and its unique business reference to off-chain entitlements, including finality, replay and reorg handling. 5. Run an allowlisted, capped phase-1 canary and reconcile every HRN transfer and license before expanding access. 6. Add settlement, signer, RPC, finality, reorg and entitlement monitoring with tested pause, incident and refund/recovery procedures. 7. Keep arena entry, prizes and LLM billing in Demo/Test mode; any HRN expansion requires a separate review and public policy update. 8. Publish a complete machine-readable OpenAPI specification and strengthen creator reputation and sandbox controls. The roadmap is directional and may change as the demo produces operational evidence. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://harena.gitbook.io/harena-docs/roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.