Loading prices…
🔥BULLISH

HashKey Cloud Backs Stacks Genesis Bond for BTC Yield

Self-custodial BTC time-locked on Bitcoin's base layer is the structural pitch, but the ~3% target yield is paid in STX and rides on Stacks miner economics, not a clean native return.

HashKey Cloud will deploy Bitcoin in Stacks' Genesis Bond pilot, becoming the second named institution to participate, founder Muneeb Ali said on Aug. 27. The Asian infrastructure provider will time-lock BTC on Bitcoin's base layer, retain the keys, and pair the position with STX worth roughly 5% of the committed Bitcoin. The bond targets about 3% annualized from BTC committed by Stacks miners and is expected to go live around Sept. 10.

Why it matters

The structural pitch is self-custody. The BTC sits in a time-locked output on Bitcoin, not with a borrower or wrapper, and the participant keeps the keys for the full term. An early exit returns the BTC principal but ends the yield, while the paired STX stays locked for the term, so the two legs carry different liquidity constraints. The yield is not native to Bitcoin, though. It is funded by STX block rewards that Stacks miners earn for producing blocks, so payouts depend on miner economics, network activity, and the STX market. Across 24 reward cycles (roughly six months), a realized target would deliver about 1.44% of locked BTC.

The first bond runs inside a managed bootstrap. During PoX-5, the Stacks Endowment sets capacity, target yield, and the BTC-to-STX ratio for each bonding period. A future PoX-6 proposal would replace those managed settings with an algorithmic, permissionless auction.

Market impact

HashKey's name establishes institutional participation; its allocation and the realized payouts will determine how much weight that signal carries. The PoX-5 codebase was audited by Trail of Bits, Clarity Alliance, and Asymmetric Research, but an open medium-severity issue in the official stacks-core repository identifies a flaw in the bond rollover path. A participant moving to a later bond could remain credited with old reward shares after withdrawing the collateral behind them, leaving other participants with a smaller share of the final-cycle reward. The bug keeps the participant's native BTC under their keys, so it does not break ordinary enrollment, but a public fix ahead of the rollover window looks important. Block 966,350 will start putting numbers to the test.

Related tokens
$BTC $STX

Frequently asked questions

  1. What is Stacks' Genesis Bond?

    It is a pilot protocol bond that lets participants time-lock BTC on Bitcoin's base layer, retain custody, and pair the position with STX worth about 5% of the BTC to target roughly 3% annualized. The first bond is expected to go live around Sept. 10.

  2. Is the yield actually native to Bitcoin?

    No. The principal sits self-custodially on Bitcoin, but the yield is paid from BTC committed by Stacks miners who earn STX block rewards. Payouts depend on miner economics, network activity, and the STX market.

  3. What happens if a participant exits the bond early?

    An early exit returns the BTC principal and ends the remaining yield, but the paired STX stays locked for the full term. The two asset legs therefore carry different liquidity constraints.

  4. Who audited the Stacks Genesis Bond code?

    The PoX-5 codebase was audited by Trail of Bits, Clarity Alliance, and Asymmetric Research. An open medium-severity issue in stacks-core identifies a flaw in the bond rollover path that has not yet been publicly mitigated.

  5. When does the pilot start producing real numbers?

    The bond is expected to begin around Sept. 10, with on-chain commitments and weekly distributions visible from launch. Block 966,350 is the first checkpoint where the design starts producing measurable numbers.

Source attribution
Aggregated from CryptoSlate · Verified · Last refreshed 1h ago
Open original →