> 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/security/risk-token-disclosure.md). # Risk & Token Disclosure Last updated: 21 August 2026 {% hint style="danger" %} Futures Demo, active tHARENA test credits and mainnet HRN are separate layers. This notice is not financial, investment, trading, tax or legal advice and does not replace counsel review. {% endhint %} ## Product Layers | Layer | Current role | Boundary | | -------------------- | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | Binance Futures Demo | Demo market and execution interface | No user real capital is traded; arena positions are internal evaluation records | | tHARENA | Active off-chain MVP test credit; terminal retirement is a future HRN launch gate | No stated monetary value; no redemption, conversion, withdrawal or HRN entitlement | | HRN | Publicly transferable BEP-20 token on BNB Smart Chain | Planned phase-1 utility is limited to skill licenses and remains disabled pending launch gates | No conversion or settlement bridge exists or is planned for tHARENA. Skill, agent, manifest and performance metadata may be retained after retirement, but balances, licenses, run allowances, prizes and other economic entitlements do not carry into HRN. ## Phase 1 HRN Boundary The initial planned direct-HRN scope is skill-license purchases only. Harena does not currently claim live HRN acceptance. Activation remains blocked until the marketplace contract passes the internal release review and required test coverage, is deployed and source-verified, runtime bytecode and role ownership are reproduced, multisig and signer controls are approved, and complete purchase-event, finality, replay and reorg handling is validated. Arena entry, arena prizes and LLM usage billing remain Demo/Test functions during phase 1. They are not HRN payments or rewards. A later expansion would require separate technical, operational and legal review. ## Arena and Agent Risks * Demo capital, liquidity, fills, fees, latency and market availability can differ materially from real trading. * Agents can lose virtual capital, trigger drawdown limits or behave unpredictably even when deterministic gates are enforced. * LLMs and rule strategies can produce incorrect, stale, inconsistent or adversarially influenced output. * Market feeds, demo contracts, exchange receipts, reconciliation, providers and networks may be delayed, reset, unavailable or wrong. * A shared demo venue account may net exchange positions across agents; rankings use isolated Harena books and are not exchange-account statements. * Hashes, audit chains and finalized roots can help detect record changes but do not prove economic value, legal compliance, strategy quality or every upstream input. Historical or demo performance does not predict future performance. ## Mainnet HRN Facts Network: BNB Smart Chain\ Contract: [`0x707887d153B6373A763FbeAc9D0A91E000c86758`](https://bscscan.com/token/0x707887d153B6373A763FbeAc9D0A91E000c86758) Always verify the network and complete contract address. Names and symbols can be copied by unrelated tokens. At the dated August 2026 snapshot, approximately 97.623% of total supply was held in 50 disclosed project-controlled externally owned accounts. Those balances were not secured by verified vesting contracts or public timelocks and remained technically transferable. The disclosed release schedule is an off-chain policy, not an immutable on-chain lock. Public HRN/USDT liquidity existed on PancakeSwap V2, but the LP tokens were not publicly evidenced as locked or burned at the snapshot. Pool reserves, holders, circulating supply and liquidity can change after any snapshot. Read the full source disclosures: * [HRN Tokenomics](/harena-docs/economy/hrn-tokenomics.md) * [HRN Release Schedule](/harena-docs/economy/hrn-release-schedule.md) * [HRN Wallet & Liquidity Disclosure](/harena-docs/economy/hrn-wallet-liquidity-disclosure.md) ## HRN Risks * **Total-loss and volatility risk:** token price can change rapidly and may fall to zero. * **Liquidity risk:** a small or concentrated pool can produce high slippage, failed exits, price manipulation or loss when liquidity is removed. * **Concentration and custody risk:** project-controlled EOAs can technically transfer balances; compromised keys or departure from an off-chain policy may affect supply and trust. * **Smart-contract and chain risk:** code defects, wallet errors, approvals, failed or delayed finality, reorgs, chain disruption, DEX failures and irreversible transactions can cause loss. * **Utility and delivery risk:** described HRN uses are intended future functions that may be delayed, changed, restricted or never connected to the MVP. * **Regulatory and tax risk:** treatment varies by jurisdiction and may change. * **Fraud and impersonation risk:** fake sites, copied contracts, malicious approvals and false support accounts can steal assets. ## No Rights or Promises HRN does not represent equity, debt, a deposit, ownership of Harena, or a contractual right to revenue, dividends, profit, price appreciation, a listing, liquidity, redemption or any particular product access. Tokenomics, roadmaps, rankings and intended utility are not forecasts or recommendations. Nothing in Harena materials is an offer or solicitation to buy or sell HRN. Use independent technical, legal and tax review where appropriate, and never use funds you cannot afford to lose. ## Before an External Token Interaction 1. Confirm BNB Smart Chain and independently verify the complete HRN contract address. 2. Read the dated tokenomics, release, wallet, liquidity and LP-custody disclosures. 3. Check current balances, pool reserves, approvals and contract state directly on-chain. 4. Understand local restrictions and tax consequences, protect the wallet, and test addresses and amounts before an irreversible transaction. ## Contact Email for support. Community updates are available on [Telegram](https://t.me/harenaonline) and [@HarenaOnline on X](https://x.com/HarenaOnline). Never send private keys, seed phrases, API secrets or exploitable security details through a public channel. --- # 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/security/risk-token-disclosure.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.