Hybla · Short white paper
A better reward for good work.
A Hive-derived economic experiment, built to run alongside Hive. A different set of incentives, on an independent chain.
Selected direction. Unresolved parameters are called out below. View the full decision register
01 / The purpose#
Hybla aims to make exceptional creative work worth pursuing. It keeps Hive’s social-blockchain foundation while changing how supply enters the economy, how curators participate and how posts compete for rewards. The objective is a credible meritocracy: participation opens the door; earning strong support should make a meaningful difference.
02 / Reward the work that stands out#
Post rewards use the historical quadratic claim curve: claim(R) = R² + 2cR, where R is positive net reward weight after downvotes and c is a content constant still to be selected. Concentrated support earns a disproportionately larger claim on the available reward fund.
The inspiration is a Zipf-like creator economy: a few leading creators, a long tail of contributors, and a substantial prize for producing work that rises through the ranks. Top creators should feel that recognition and effort can lead to differentiated rewards. Others should have a reason to aspire to those outcomes.
This is an incentive thesis, not a promise that a formula produces Zipf’s law or measures merit. Stake concentration, attention and collusion can all shape results. The design must be judged against observed behavior.
03 / Give curators room to choose#
Positive voting mana accumulates continuously in a seven-day reservoir. A user may spend any available amount, including the entire reservoir, on one post. Small holders can save their influence for something that matters to them, without a daily voting routine.
Equal eligible contributions to the same post receive equal curation shares, regardless of voting order or arrival time before the cutoff. Discovery should not be penalized merely because someone else arrived first. The author / curator split and exact eligibility rules remain open.
04 / Keep the reward fund rolling#
Hybla retains Hive-style rolling payouts: continuous funding, individual post cashouts and a decaying recent-claims ledger. The inherited modeling baseline is seven-day cashout and a 15-day claims decay timescale. These are separate from the weekly mana budget.
A quadratic claim earns a share of an existing balance; it does not compound or create extra tokens. The launch specification must settle initial claim history, precision and final payout parameters.
05 / Make money creation explicit#
Scheduled annual issuance starts at 2% and stays there. Content, witnesses, staking and treasury allocations must fit within that schedule. The treasury starts empty, with no inherited legacy endowment. Its balances remain visible as existing supply.
Power-down takes four weeks. The initial native-to-stable conversion premium is 1%, with a debt target of 10% of the backing native asset’s market capitalization.
The issuance base, budget shares, stablecoin safeguards and debt accounting still need specification. Conversion-related issuance, interest and burns must be disclosed separately; 2% scheduled issuance is not a universal cap on every supply change.
06 / Keep rewards contestable#
Hive’s downvote mechanic remains. Stakeholders can reduce a disputed post’s net reward weight before cashout, including rewards directed through self-voting and voting rings.
This defense depends on observation and participation. It does not automatically recognize collusion, and it can be misused. Tests must cover whale capture, hidden common ownership, retaliation and the cost of defending legitimate content. The downvote budget’s integration with weekly positive mana remains engineering work.
07 / Start fairly, prove the rules#
No inherited whale airdrop. The intended routes to ownership are contribution, network work, staking or purchase. The initial supply and distribution are still to be determined. No sale or earned-genesis mechanism has been approved.
Before launch, Hybla needs a public consensus implementation, a reproducible testnet, transparent supply accounting and adversarial reward tests. This paper records selected design direction, not a completed protocol or an offer of tokens.