HashKey Cloud Signals Institutional Interest in Bitcoin Yield Pilot

HashKey Cloud will join Stacks’ Genesis Bond pilot by time-locking Bitcoin while retaining its own keys and pairing the position with STX, according to Stacks founder Muneeb Ali, who announced the move via X on Aug. 27. The commitment makes HashKey Cloud the second institution publicly tied to the program, but its allocation and eventual payouts remain undisclosed heading into a planned start around Sept. 10.

HashKey Cloud joins Stacks’ Genesis Bond pilot

Under the structure, HashKey will lock Bitcoin in a time-locked output on Bitcoin’s base layer while retaining custody of its keys, then pair that position with STX worth roughly 5% of the committed BTC. The design keeps the asset outside any lending agreement, wrapper, or third-party custody arrangement. Stacks has published an explainer on the mechanics of how Bitcoin staking works on the network.

HashKey’s specific allocation has not been disclosed. The total BTC committed across all participants is expected to become visible on-chain once the bond begins, expected around Sept. 10.

Retaining custody of the principal, however, does not make the yield itself risk-free or purely native to Bitcoin. Stacks targets roughly 3% annualized return in BTC, funded by miners competing to produce blocks, according to the primary reporting. Across a roughly six-month term spanning 24 reward cycles, that target would deliver approximately 1.44% of locked BTC if realized – a figure that depends on STX exposure, miner economics, network fees, and overall Stacks activity rather than a fixed coupon.

The two legs of the position also carry different liquidity terms. An early exit returns the BTC principal and ends the remaining yield, but the paired STX stays locked for the full term, leaving that portion exposed to STX price swings for roughly six months regardless of when the BTC leg is unwound.

Why the pilot matters for institutional Bitcoin yield

HashKey’s name gives the Genesis Bond concrete institutional participation, but a name alone is not proof of scale. Its undisclosed allocation and the bond’s realized payouts will determine how much weight this announcement actually carries as evidence of institutional demand for native Bitcoin yield.

The broader appeal is straightforward: the design reduces reliance on a borrower or custodian holding the Bitcoin itself. It avoids lending and third-party custody arrangements. But removing custodial risk does not remove risk altogether – it replaces it with STX market exposure, miner-funded payout variability, program parameters set by the Stacks Endowment, and contract risk.

For Stacks, the near-term evidence will come from three data sources: on-chain BTC commitments showing how much institutions actually place in the bond, weekly distributions showing whether miner revenue supports the target rate, and reserve data showing the buffer available if revenue falls short.

Managed parameters and PoX-5 risk

The first Genesis Bond does not run as an open market. It operates inside what Stacks describes as a managed bootstrap, with the Stacks Endowment setting each bonding period’s capacity, target yield, BTC-to-STX ratio, and allocation directly rather than letting those terms emerge from competitive bidding.

A future proposal known as PoX-6 is intended to eventually replace those managed settings with an algorithmic, permissionless auction, according to the SIP-045 specification governing the current system. Until that proposal advances, Genesis Bond tests the product within boundaries the Endowment chooses, not an open market clearing rate.

The underlying PoX-5 upgrade activated at Bitcoin block 960,230 on July 30, and Stacks says the codebase was audited by Trail of Bits and Clarity Alliance, with additional review from Asymmetric Research. Despite that scrutiny, an open medium-severity issue remains in the official stacks-core repository concerning the bond rollover path.

Near the end of a bond term, a participant rolling into a later bond can remain credited with old reward shares even after withdrawing the collateral behind them, which could shrink other participants’ share of the final-cycle reward, according to the GitHub issue tracking the flaw. The bug does not move or transfer custody of a participant’s native Bitcoin, which remains under the participant’s keys, and it does not indicate a failure in ordinary Genesis Bond enrollment. The affected code still sits in the live 4.0.1 PoX-5 contract source, making a public fix or mitigation important before the rollover window is reached.

What comes next for Genesis Bond

The bond is expected to begin around Sept. 10, with Bitcoin block 966,350 marking the point where the pilot starts producing real numbers instead of projections. From there, HashKey’s disclosed allocation – if and when it surfaces – will show the actual scale of its participation rather than just the fact of it.

On-chain BTC commitments will reveal total capital placed across all institutional participants, while weekly distribution data will show whether miner revenue is actually supporting the roughly 3% annualized target or falling short of it. Reserve figures will indicate how much buffer exists if miner economics weaken.

A public fix or mitigation for the rollover flaw in the PoX-5 contract remains an open item worth tracking before later bonding periods roll over. Until allocation figures, distribution data, and the rollover fix are all visible, HashKey’s participation establishes intent more than it proves outcome.