HashKey Cloud said on Sept. 7 that it had joined Stacks as a launch partner for self-custodial Bitcoin staking.
Summary
- HashKey Cloud joined Stacks as a Genesis Bond participant and an sBTC signer operator officially.
- The institutional Genesis Bond is scheduled to launch around September 10, according to Stacks developers.
- Bonded Bitcoin remains timelocked on Bitcoin while participants pair it with locked STX tokens separately.
- HashKey Cloud says its staking infrastructure spans more than 40 different blockchain networks globally today.
- sBTC signers coordinate Bitcoin deposits and withdrawals using a threshold-based approval system collectively onchain today.
The agreement gives the infrastructure provider two roles: participating in the inaugural Genesis Bond and joining the signer network securing sBTC.
HashKey Cloud operates under HashKey Holding Limited. Stacks founder Muneeb Ali presented the collaboration during the HashKey Cloud and Cactus Custody “Yield on Trust” event in Hong Kong.
The company says its node and staking infrastructure covers more than 40 blockchain networks. Stacks reported that HashKey Cloud manages about HK$29 billion in staked assets. These figures come from the companies and were not independently audited for the partnership announcement.
HashKey Cloud will participate in the first Genesis Bond
HashKey Cloud will join the first institutional cohort using Stacks’ new Protocol Bond system. Stacks said in an official announcement that the Genesis Bond was expected to begin around Sept. 10.
The launch date remains an estimate. Stacks has not announced an exact activation time, final capacity or participant allocations. Technical or operational conditions could also alter the schedule.
The first cohort includes institutional participants such as digital asset manager 21Shares and UTXO Management, a subsidiary of Bitcoin treasury company Nakamoto Inc. The Genesis Bond is intended to demonstrate how institutions can earn BTC-denominated rewards without transferring their Bitcoin to a centralized custodian.
Bitcoin committed to the product remains visible on its base blockchain. The arrangement should allow observers to inspect the relevant timelock transactions without relying exclusively on reports from Stacks or participating institutions.
The phrase “Bitcoin staking” requires context. Bitcoin uses proof-of-work and does not support staking through its native consensus system. The Genesis Bond does not change Bitcoin’s consensus rules.
Stacks instead uses Proof of Transfer, commonly called PoX. Stacks miners commit BTC while competing to produce blocks. The protocol distributes part of that Bitcoin to qualifying participants as rewards.
Bitcoin remains under the holder’s keys
Stacks’ PoX-5 design introduces a Protocol Bond that connects two separate commitments. The participant timelocks BTC on Bitcoin’s base layer and locks a corresponding amount of STX on Stacks.
According to the project’s technical documentation, a bond lasts 12 Stacks reward cycles, or approximately six months. The Bitcoin remains in a wallet controlled by the holder’s keys rather than moving to a centralized custodian or wrapped asset.
The participant must also lock STX through a signer-manager contract. The two positions are cryptographically associated and operate together for the bond term.
PoX-5 permits only one active staking position for each Stacks principal. A participant cannot use the same principal for an STX-only position and a Protocol Bond simultaneously. The protocol also prevents one principal from holding two concurrent bonds.
The documentation allows early withdrawal. However, participants leaving before the scheduled end of a term forfeit their remaining rewards for that cycle. Recovering the BTC principal still requires the holder’s signature.
Rewards initially accrue as sBTC. A participant may request native BTC by supplying a Bitcoin payout address, provided the selected signer manager supports base-layer withdrawals.
Native BTC settlement is not available under every configuration. If the withdrawal cannot be processed within the participant’s maximum transaction-fee setting, the payment falls back to sBTC.
As crypto.news reported, Stacks is targeting an annualized Bitcoin yield near 3% during the initial phase. The rate is a protocol target, not a guaranteed return. Actual rewards may vary with miner commitments, available capacity and network conditions.
HashKey Cloud will help secure sBTC transfers
HashKey Cloud will also operate as a signer for sBTC, the Bitcoin-backed asset used within the Stacks ecosystem. Stacks previously confirmed that HashKey Cloud, Ankr and The Tie had joined the signer set.
sBTC is designed to represent BTC on Stacks at a one-to-one ratio. Users can deploy it within Stacks applications while the underlying Bitcoin remains governed by the network’s signer system.
Signers collectively authorize deposits and withdrawals between Bitcoin and Stacks. No individual signer can independently move the BTC backing sBTC.
Stacks said the system maintained a 70% approval threshold throughout the latest signer rotation. Operations such as withdrawals require approval representing at least 70% of participating signer weight.
Adding HashKey Cloud brings an Asia-based infrastructure provider into the signer group. Stacks described the expansion as improving institutional access and distributing operating responsibility across additional companies and regions.
Those benefits remain Stacks’ assessment. A larger signer set does not remove every technical or governance risk associated with sBTC.
Users still depend on enough signers remaining available and following the protocol correctly. Software failures, signer outages or coordination problems could delay deposits and withdrawals. Smart-contract faults could also affect services built around sBTC.
Self-custody reduces exposure to a single custodian, but it does not eliminate risks arising from Stacks contracts, wallet software, signer managers or the sBTC system.
Genesis Bond access will remain limited initially
Stacks plans to introduce Protocol Bonds in stages. Initial Genesis Bond access focuses on institutions and professional market participants rather than unrestricted retail participation.
The project’s staking guidance says bond capacity will be allocated to approved partners during the bootstrap phase. Some capacity may become available through selected pooling providers.
Wallet compatibility is another requirement. Leather and Xverse support PoX-5 functions, while Ledger users need Stacks application version 0.26.15 or later for transactions carrying the new spending conditions.
Participants must also consider the prepare phase at the end of each reward cycle. During the final 100 Bitcoin blocks, the protocol rejects new staking transactions, position updates and withdrawal requests.
HashKey Cloud has not disclosed how much BTC or STX it plans to commit. The company also has not published participation fees, customer eligibility requirements or a list of supported jurisdictions.
Its announcement cautioned that Bitcoin staking services may be unavailable in some regions because of local laws. HashKey Cloud did not guarantee any investment return.
The Genesis Bond’s expected launch is the next event to watch. Confirmation of the activation time, committed Bitcoin, participating institutions and available capacity would provide the first measurable evidence of demand for the product.
