HivemindOS manual
Revenue Allocations And Treasury Boundaries
This page keeps its existing filename for link compatibility. The current policy is a simple two-allocation model, not a staking-income program.
Current 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 do not form one discretionary treasury bucket, and the treasury is not the source of HIVE purchases.
Recognized Revenue Boundary
Recognized platform revenue is narrower than customer collections or transaction volume. It excludes directly attributable pass-through costs, refunds, and reversals. Marketplace gross merchandise value is not recognized platform revenue; only HivemindOS’s earned platform fee is counted. Purchased credits are recognized only when consumed.
The allocation basis is server-owned and published per service in the official commercial catalog: realized margin for most managed services, recognized platform revenue for others.
Official hosted infrastructure calculates and records both allocations. A downloadable client, local environment value, connected user wallet, or client-supplied revenue claim cannot choose the allocation basis, amount, or recipient.
HIVE Buyback Rail
The buyback rail purchases HIVE from its own separate 15% allocation. Confirmed purchases are published in the HIVE Buyback Ledger; pending allocations, failed batches, and unconfirmed transactions do not count as HIVE bought.
HivemindOS does not burn HIVE. A buyback is not a distribution, staking payment, price floor, liquidity guarantee, or promise of token appreciation.
Company Treasury Rail
The separate 15% treasury allocation is company property. This tokenomics policy does not prescribe one fixed use for treasury assets.
The treasury allocation 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 purchase HIVE
Staking Separation
The staking vault holds user principal. It does not fund buybacks or the company treasury. Holding or staking HIVE does not create a balance or claim against either revenue allocation.
The six staking tiers provide product benefits only: Honey earning multipliers, free-agent usage multipliers, and member pricing advertised as up to 61% off on participating services. They provide no yield, revenue share, ownership, binding governance, or treasury claim.
Change And Receipt Policy
Allocation definitions, percentages, cadence, minimums, caps, and execution may change, pause, or end prospectively because of legal, regulatory, tax, accounting, corporate, security, liquidity, market-integrity, reserve, solvency, or operational requirements.
Material changes are published with an effective date. Completed on-chain purchases and historical receipts remain part of the public record. Continuation of an operating policy is not a contractual right of holding or staking HIVE.