Honey, HIVE, And Treasury

HivemindOS has three separate things that are never one balance: Honey, Hivemind Cloud credits, and HIVE. This page explains each one and how revenue is allocated.

Honey

Honey records useful, verified participation, such as reviewed agent work, accepted open-source contributions, testing, documentation, or completed bounties. Self-reported activity and unobserved output do not earn Honey. Model usage earns Honey only through a legacy pool: it still records 1 Honey per 1,000,000 model tokens, capped at 50,000 tokens a day, until that pool is used up.

How Honey is earned:

• Community Hive Brain: 0.1 Honey for each distinct copy-trading outcome that passes hosted verification. Unverified, duplicate, and retried submissions earn nothing. The contributing wallet must link to a HivemindOS workspace; until it does, the reward waits as pending.
• Telegram recognition: members with a signature-verified identity can give a fixed, scarce Honey recognition for a named contribution. Daily, pair, recipient, cooldown, and global budget limits apply.
• Published API receipts: 5 Honey for each published receipt, up to 3 a week.
• Feedback: 2, 5, or 10 Honey depending on what was built from it, and never more than 25 for one piece of feedback.
• X engagement: 1 Honey a day per account, up to 3 a week.
• HiveVerse finds: 1 Honey for each find.
• HivePunkz share to X: 10 Honey.
• Historical HIVE tips: past tip-receiver rank may be recorded at 1 Honey per 1,000,000 HIVE received.
• Legacy model-usage pool: 1 Honey per 1,000,000 model tokens, capped at 50,000 tokens a day, until the pool is used up.

Source labels (mission, verified work, peer recognition, learning, historical seed) show where Honey came from. They do not create different kinds of Honey.

What Honey does:

• More free-agent usage. Lifetime Honey raises a workspace’s daily free-agent request and token allowance, from 1.10× at 5 Honey up to a capped 2.00× at 200: 5, 10, 25, 50, 100, and 200 Honey give 1.10×, 1.20×, 1.35×, 1.50×, 1.75×, and 2.00×. This allowance and a HIVE staking allowance do not stack; the higher one applies. It is revocable service access, not stored value or a withdrawal right.
• Staking multiplies Honey. An active HIVE staking tier multiplies qualifying Honey earned: 1.00×, 1.10×, 1.25×, 1.45×, 1.70×, and 2.00× from Honeybee through Queen Bee. A Founding Bee adds +0.5× on top of the tier, capped at 2.5×.

HivemindOS-controlled infrastructure calculates Honey totals and tiers from verified records. Local state cannot grant Honey, a tier, or contribution evidence.

Honey does not automatically convert to HIVE. Honey-to-HIVE exchange and claim routes stay off unless a separately authorized hosted policy turns them on, and the product never shows an unavailable conversion as “ready to claim.”

Hivemind Cloud credits

Credits are how customers pay for managed services: managed agents, hosted models and APIs, app publishing, managed media and tools, and other HivemindOS-operated services.

Credits are spend-only, nontransferable, not redeemable for cash, recorded on the server, and funded only by verified payments. Prices and balances are shown in ordinary dollars, not as token rewards.

HIVE

HIVE may support optional community identity, payments, staking-based Honey earning multipliers, free-agent usage multipliers, member pricing of up to 61% off on participating services, marketplace settlement, or bounties, where those features are available and legally reviewed. Exact service prices remain server-owned.

You do not need HIVE to run HivemindOS locally, buy Hivemind Cloud services, join a paid workspace, use enterprise features, or bring a provider key. HIVE is not company ownership. See HIVE Staking And Community Tiers for tier details.

Paying with HIVE

Pay with $HIVE takes 10% off a credit top-up. The HIVE you pay goes to the company treasury as it is: it is not sold, and it is not burned. Credits bought with HIVE create no buyback or treasury allocation when they are spent. Paying with another token carries a 5% fee.

Revenue allocation

Customer collections are not automatically platform revenue. Recognized platform revenue excludes pass-through costs, refunds, and reversals. Marketplace gross merchandise value is not platform revenue; only HivemindOS’s earned fee counts. Purchased credits are recognized only when consumed.

Each paid service has a server-owned allocation basis, published in the official commercial catalog: realized margin for most managed services, recognized platform revenue for others. From that basis:

server-owned per-service allocation basis
├─ 15% -> HIVE buybacks
├─ 15% -> company treasury
└─ remainder -> outside the tokenomics allocation, with no fixed use assigned here

• HivemindOS allocates 15% of each service’s server-owned allocation basis to HIVE buybacks.
• A separate exact 15% of the same server-owned allocation basis goes to the company treasury.
• Two exceptions apply. Credits bought with HIVE create no buyback or treasury allocation when they are spent. HiveVerse home upgrades split 40% to HIVE buyback and burn, 40% to the HivePunks reward pot, and 20% to the company treasury.
• The treasury does not fund HIVE buybacks. Each rail has its own accounting and receipts.
• No user wallet, staked principal, local setting, or client revenue claim can choose either amount or recipient.
• Confirmed purchases are published in the HIVE Buyback Ledger. Pending or failed purchases do not count.
• Since 2026-09-30, the HIVE each confirmed purchase buys is burned: the exact amount is sent to 0x000000000000000000000000000000000000dEaD in a separate transaction, published on the same ledger. Purchases made before that date were not burned. That HIVE, about 9.98M, is held.
• Hive Research’s first paid production run produced one confirmed HIVE purchase on Base under its earlier app-specific policy. That receipt stays public; new Hive Research revenue follows the platform-wide 15% buyback allocation.

The treasury allocation remains company property. It creates no holder or staker ownership, redemption right, revenue share, governance right, or claim on treasury assets. Buybacks do not promise a token price, liquidity, profit, or return. More detail: Revenue Allocations And Treasury Boundaries.

Where HIVE is burned

Every burn sends HIVE to 0x000000000000000000000000000000000000dEaD.

A burn is a recorded on-chain transfer. It is not a promise about price, value, or return.

HivePunks

HivePunks are 1,111 NFTs on Base, and the collection sold out. Each mint cost 10 USDC: 70% feeds the HivePunks reward pot over 8 weeks, and 30% goes to the HivePunks treasury. The pot is converted to tokenized NVDA and paid weekly to bees that are clocked in. The 7.5% royalty goes entirely to the pot. HivemindOS also pays 25% of HIVE creator fees on daily HIVE trading volume above $20,000 into the pot, capped at $15,000 a quarter for 8 quarters. What the pot pays depends on what it receives; no amount is promised.

Agent coins

Agent coins carry a 2% trading fee. The first $20 of fees goes to the agent’s thinking budget. After that, each fee splits 60% to the agent’s thinking, 15% to whoever holds the agent’s NFT, 15% to buy HIVE that is burned, and 10% to the HivemindOS treasury. Coin holders receive none of the fee.

Tokenomics Policy Changes

Tokenomics is an operating policy, not an immutable promise. Allocation formulas, buyback amounts and timing, staking benefits, tier thresholds, and eligibility may change, pause, or end when needed for legal, regulatory, tax, accounting, corporate, security, liquidity, market-integrity, reserve, provider, or operational reasons.

Material changes are published with an effective date and apply going forward unless the law requires otherwise. Completed on-chain actions and historical receipts remain part of the public record and are not rewritten. Holding or staking HIVE gives no contractual right to any particular formula, buyback, benefit, tier, or schedule.