HivemindOS manual
Revenue Allocations And Treasury Boundaries
This is the canonical page for where HivemindOS revenue goes. There are two fixed allocations, one for HIVE buybacks and one for the company treasury, with two exceptions described below. Neither is a staking-income program.
The allocation
| Revenue rail | Allocation | Boundary |
|---|---|---|
| HIVE buybacks | 15% of the per-service allocation basis | Separate purchase rail; not funded by the company treasury |
| Company treasury | 15% of the per-service allocation basis | Company property; does not fund HIVE buybacks |
| Outside tokenomics allocation | Remainder of the per-service allocation basis | This policy assigns no fixed use |
The two 15% allocations are exact and separate. They are not one shared bucket, and the treasury is not the source of HIVE purchases.
Two exceptions apply:
- Credits bought with HIVE create no buyback or treasury allocation when they are spent. The HIVE paid for them goes to the company treasury as it is, without being sold.
- HiveVerse home upgrades split 40% to HIVE buyback and burn, 40% to the HivePunks reward pot, and 20% to the company treasury.
What the allocation is based on
Each service’s allocation basis is server-owned and published in the official commercial catalog: realized margin for most managed services, recognized platform revenue for others.
Recognized platform revenue is narrower than what customers pay or total transaction volume:
- It excludes pass-through costs, refunds, and reversals.
- For marketplaces, only HivemindOS’s earned fee counts, not gross merchandise value.
- Purchased credits count only when they are spent.
HivemindOS’s hosted infrastructure calculates and records both allocations. The app, a local setting, a connected wallet, or a client revenue claim cannot choose the basis, amount, or recipient.
HIVE buybacks
The buyback rail buys HIVE with its own 15% allocation. Confirmed purchases are published in the HIVE Buyback Ledger. Pending allocations, failed batches, and unconfirmed transactions do not count.
How a buyback runs
- Each charge waits 7 days before its revenue counts as matured.
- Every Sunday at 08:00 UTC, matured revenue is bought in batches of $5 to $1,000.
- A batch runs only after the revenue it covers has been reconciled.
- The HIVE each purchase buys is then burned in its own transaction, shown on the ledger.
Since 2026-09-30, HIVE bought by buybacks is burned: the exact amount each purchase buys is sent to the burn address 0x000000000000000000000000000000000000dEaD in its own transaction, published on the HIVE Buyback Ledger. Purchases made before that date were not burned. A buyback or burn is not a distribution, staking payment, price floor, liquidity guarantee, or promise of appreciation.
Company treasury
The treasury allocation is company property, and this policy does not fix how it is used. It gives HIVE holders and stakers no:
- ownership of company or treasury assets
- redemption right
- share of revenue
- automatic distribution
- binding governance or control over treasury decisions
- promise that treasury funds will buy HIVE
Staking is separate
The staking vault holds user principal. It funds neither buybacks nor the treasury, and staking creates no claim on either. The six tiers give product benefits only; see HIVE Staking And Community Tiers.
Changes
Allocation definitions, percentages, timing, minimums, caps, and execution may change, pause, or end going forward for legal, regulatory, tax, accounting, corporate, security, liquidity, market-integrity, reserve, solvency, or operational reasons. Material changes are published with an effective date. Completed on-chain purchases stay on the public record. Holding or staking HIVE gives no contractual right to the policy continuing.