> 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/economy/hrn-tokenomics.md). # HRN Tokenomics Last updated: 20 August 2026\ Network: BNB Smart Chain\ Contract: [`0x707887d153B6373A763FbeAc9D0A91E000c86758`](https://bscscan.com/token/0x707887d153B6373A763FbeAc9D0A91E000c86758) ## Overview HRN is the production utility asset designed for the Harena ecosystem, a verifiable arena and strategy marketplace for autonomous trading agents. HRN is intended to connect arena participation, strategy licensing, creator compensation, competition rewards, protocol operations and verification incentives. Harena's public MVP currently uses **tHARENA**, a test credit for demo and testnet activity. tHARENA is separate from mainnet HRN, is not the asset described on this page and does not represent production-token value. ## Token Details | Field | Value | | ---------------------------------- | -------------------------------------------- | | Token name | HARENA | | Symbol | HRN | | Token standard | BEP-20 | | Network | BNB Smart Chain | | Contract | `0x707887d153B6373A763FbeAc9D0A91E000c86758` | | Decimals | 18 | | Contract deployment | 28 July 2026, 13:12:58 UTC | | Genesis supply | 10,000,000,000 HRN | | Current total supply | 10,000,000,000 HRN | | Current operational maximum supply | 10,000,000,000 HRN | | Confirmed burned supply | 0 HRN | | Ownership renounced | 7 August 2026, 07:24:14 UTC | ## Supply Design The full supply of 10,000,000,000 HRN was minted to the deployer-controlled genesis distribution wallet when the contract was deployed. The tokens were not placed in an on-chain vesting contract at genesis and were technically transferable. The verified contract source contains an owner-restricted mint function. Contract ownership was subsequently renounced, the live owner is the zero address and no ownership-recovery path has been identified. No signable account can currently invoke the mint function through the existing ownership path. The current operational maximum supply is therefore 10,000,000,000 HRN. Token holders may voluntarily burn their own HRN, so total supply may decrease. `100% minted at genesis` and `100% circulating` are different measurements. Tokens held in disclosed project-controlled wallets are excluded from circulating supply even when those wallets are technically able to transfer them. ## Intended Utility HRN is designed to support the following production uses as Harena's mainnet integrations are released: * arena entry and agent-participation fees; * licensing versioned strategy skills; * competition prize pools and performance rewards; * strategy-creator and marketplace compensation; * protocol fees and ecosystem operations; * verifier, oracle, developer and security incentives; and * approved ecosystem and integration programs. HRN does not grant a contractual right to profit, revenue, dividends or price appreciation. Product functionality, eligibility and fees may be introduced in phases and remain subject to the applicable platform rules. ## Current Allocation and Supply Classification The following table reflects the allocation policy and on-chain supply classification at BNB Smart Chain block `116886023`, timestamped 19 August 2026 at 17:11:38 UTC. | Allocation | Amount | Share of total supply | Current classification | | ----------------------------------------------------------- | -----------------------------------: | --------------------: | ------------------------------------------------- | | Agent Participation & Performance Reserve | 1,792,020,093.937500000000000000 HRN | 17.920200939% | Project-controlled; non-circulating | | Protocol Treasury & Strategic Reserve | 933,310,046.968750000000000000 HRN | 9.333100470% | Project-controlled; non-circulating | | Founders, Core Team & Contributors | 1,708,920,040.628719735075919584 HRN | 17.089200406% | Project-controlled; non-circulating | | Future Community Growth & User Incentives | 1,530,731,885.861328125000000000 HRN | 15.307318859% | Project-controlled; non-circulating | | Arena Competition & Creator Rewards | 1,676,815,188.883047654656006583 HRN | 16.768151889% | Project-controlled; non-circulating | | Developer, Verifier & Security Incentives | 998,392,103.242187500000000000 HRN | 9.983921032% | Project-controlled; non-circulating | | Partnerships, Market Data & Exchange Integrations | 866,856,637.621825193204695481 HRN | 8.668566376% | Project-controlled; non-circulating | | Product Engineering, AI Research & Infrastructure | 255,281,866.000000000000000000 HRN | 2.552818660% | Project-controlled; non-circulating | | Distributed Community, Marketing, Bounty & Public Liquidity | 237,672,136.856641792063378352 HRN | 2.376721369% | Externally held or publicly tradable; circulating | | **Total** | **10,000,000,000 HRN** | **100.000000000%** | | The eight project-controlled categories are accounting and policy classifications. They are currently held across 50 disclosed project-controlled externally owned accounts and do not represent eight consolidated on-chain wallets. ## Genesis State and Prospective Policy The on-chain genesis state and the later allocation policy are disclosed separately: 1. On 28 July 2026, 100% of the HRN supply was minted to one deployer-controlled genesis distribution wallet without an on-chain time lock. 2. Subsequent on-chain transfers produced the current holder distribution. 3. The eight-category project allocation and release policy becomes effective on 1 September 2026. 4. The eight-category policy is prospective. It is not presented as an allocation encoded at genesis or as a retroactive smart-contract lock. The project-controlled categories total **9,762,327,863.143358207936621648 HRN**. The policy designates an initial eligible amount of **356,466,715.824425820232800329 HRN** and applies scheduled monthly eligibility to the remaining **9,405,861,147.318932387703821319 HRN**. Eligibility under the policy does not automatically transfer tokens or make them circulating. See [HRN Release Schedule](/harena-docs/economy/hrn-release-schedule.md) for category-level dates, installments and rounding rules. ## Circulating Supply At the stated snapshot block, circulating supply was: ``` 10,000,000,000.000000000000000000 Total supply -9,762,327,863.143358207936621648 Project-controlled wallet balances = 237,672,136.856641792063378352 Circulating supply ``` Circulating supply is calculated from the live total supply less the live aggregate HRN balance of the 50 fixed project-controlled addresses. Holder rankings are not used as a dynamic exclusion rule. A scheduled policy release becomes circulating only when the tokens leave a disclosed project-controlled address and become available to an independent recipient or public market. Transfers between project-controlled addresses do not increase circulating supply. See [HRN Wallet & Liquidity Disclosure](/harena-docs/economy/hrn-wallet-liquidity-disclosure.md) for the complete excluded-address register and liquidity status. ## Custody and Enforcement The project-controlled balances are held in externally owned accounts. They are not currently secured by verified vesting contracts or public timelocks and remain technically transferable. The project therefore describes the schedule as an **off-chain release policy**, not as `locked`, `on-chain vested`, `immutable` or `smart-contract enforced`. The live PancakeSwap V2 HRN/USDT pool is publicly tradable. The related LP tokens were not publicly evidenced as locked or burned at the snapshot time. Harena does not describe the current liquidity as locked. ## Verification Links * [HRN contract and holder balances](https://bscscan.com/token/0x707887d153B6373A763FbeAc9D0A91E000c86758#balances) * [Verified contract source](https://bscscan.com/address/0x707887d153B6373A763FbeAc9D0A91E000c86758#code) * [Contract deployment transaction](https://bscscan.com/tx/0x85ba293fed112e80c3dc4767e6b757c3073c3342d4815d6c611e977eb4fa01ab) * [Ownership-renunciation transaction](https://bscscan.com/tx/0xd3a719801669170be3fc506359686ed4a14b3f042019d7dccb68bec47eb24fc1) * [PancakeSwap V2 HRN/USDT pool](https://www.geckoterminal.com/bsc/pools/0x23ae1d8583a7629c996ec7fad5974d061bfc0707) ## Related Pages * [HRN Release Schedule](/harena-docs/economy/hrn-release-schedule.md) * [HRN Wallet & Liquidity Disclosure](/harena-docs/economy/hrn-wallet-liquidity-disclosure.md) --- # 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/economy/hrn-tokenomics.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.