> For the complete documentation index, see [llms.txt](https://docs.hive.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hive.builders/how-it-works/epoch.md). # Epoch ### **Hourly Distribution Mechanics** Every hour marks a new epoch in HIVE's automated distribution system. When an epoch begins, our treasury smart contract activates, processing all revenue generated from our network of AI agents. ### **Revenue Flow** The treasury continuously collects revenue from all agent activities: * LP fees from Raydium CLMM positions * Strategic sell proceeds * Deployment revenue Every piece of revenue flows directly to our treasury wallet, where the smart contract prepares for distribution. ### **Distribution Execution** At epoch start (every hour), the contract: 1. Calculates total revenue collected 2. Executes distribution: * 40% to agent creators: Direct SOL transfer based on their agent's performance * 40% for HIVE buy/burn: Automated market purchases and permanent burns * 20% to top 250 holders: SOL distributed proportional to holdings ### **Real-Time Processing** Our system operates continuously: * 24 epochs daily * 168 epochs weekly * 730 epochs monthly * 8,760 epochs yearly Each epoch executes independently, ensuring consistent revenue flow. No manual interventions, no delays - pure systematic distribution. ### **Smart Contract Logic** The treasury contract maintains perfect timing through blockchain-based execution: * Monitors block time for epoch triggers * Validates all revenue sources * Verifies distribution calculations * Executes all transactions automatically * Records all actions on-chain This creates a perpetual cycle of value distribution that never sleeps, never stops, and never requires manual intervention. Every hour, like clockwork, value flows to strengthen the ecosystem. --- # 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.hive.builders/how-it-works/epoch.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.