> For the complete documentation index, see [llms.txt](https://docs.vicfoundation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vicfoundation.com/readme.md). # What is HERO? ## HERO Whitepaper v2.0 ### Executive summary HERO is a community-first token on PulseChain and Base. It powers [herobase.io](https://herobase.io) and the broader HERO ecosystem. HERO is built to combine product utility, fee-driven value capture, and mission-led growth. The goal is simple: create a token people use, a platform people return to, and an ecosystem that compounds over time. ### Mission and vision HERO supports the VIC Foundation, a 501(c)(3) focused on veterans. The mission is to build useful crypto products while funding real-world impact. The vision is a self-reinforcing ecosystem. Platform usage drives token activity. Token activity strengthens the flywheel. That momentum supports veterans through the VIC Foundation. ### Token economics HERO uses a simple fee model designed for long-term alignment. * Buy fee: 5% * Sell fee: 10% * Sell fee decay: the sell fee decreases over time for long-term holders This structure rewards conviction and discourages short-term churn. It also gives HERO room to fund burns, liquidity, staking, and ecosystem growth. For deeper mechanics, see [Overview](/token/overview.md) and [Liquidity & Fees](/token/liquidity-and-tax.md). ### The HERO flywheel HERO runs a buy-and-burn engine that turns activity into sustained buy pressure. A portion of value flows into native coin, then back into HERO through scheduled market buys. Those tokens are burned permanently. The flywheel works in four steps: 1. Users trade and use HERO products. 2. Fees route value into the ecosystem. 3. The buy-and-burn engine buys HERO on market. 4. Purchased tokens are burned, reducing supply over time. This loop gives HERO a clear on-chain value engine. See [Buy & Burn Engine](/token/buy-and-burn.md) for the full breakdown. ### Platform features herobase.io is the operating layer around HERO. It is built to give the token real utility, not just narrative. Key features include: * DEX aggregation for more efficient swaps * Staking and reward flows for aligned holders * DCA tools for automated accumulation * NFTs with ecosystem utility * ABLE Bots for automation and product expansion * Governance for community participation Together, these features connect usage, incentives, and ownership inside one ecosystem. ### Build the Tech HERO launched on November 11, 2025. The launch date was Veterans Day by design. The project was launched by founder VETS and the Build the Tech team. The focus is execution first: ship useful products, grow community participation, and keep the ecosystem moving forward. ### Security Security is part of the HERO baseline. The project reports a Codex score of 96/100 and KYC certification. Smart contract risk still exists in every on-chain system. Review the full [Security & Risk](/security-and-risk.md) page before interacting with any contract. ### Deployment addresses #### Base * HERO Token: [0x00Fa69ED03d3337085A6A87B691E8a02d04Eb5f8](https://basescan.org/address/0x00Fa69ED03d3337085A6A87B691E8a02d04Eb5f8#code) * HERO Buy & Burn: [0x67bEF0A8Be3ef576bF4ab2D904FCbe82E9846670](https://basescan.org/address/0x67bEF0A8Be3ef576bF4ab2D904FCbe82E9846670#code) #### PulseChain * HERO Token: [0x35a51Dfc82032682E4Bda8AAcA87B9Bc386C3D27](http://scan.pulsechain.com/address/0x35a51Dfc82032682E4Bda8AAcA87B9Bc386C3D27?tab=contract_code) * HERO Buy & Burn: [0x9016a0DAA30bD29A51a1a2905352877947f904E9](http://scan.pulsechain.com/address/0x9016a0DAA30bD29A51a1a2905352877947f904E9?tab=contract_code) See [Deployment Addresses](/deployment-addresses.md) for the dedicated address reference page. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.vicfoundation.com/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.