Sui’s Hashi Bitcoin Project Reaches Testnet, but the $500 Million Figure Lacks Confirmation
Hashi’s testnet is live, the Sui Foundation says. More than 20 launch partners have committed to building on the project and deploying capital, according to the Foundation. Its July 22, 2026 announcement does not say those commitments total $500 million. It also reports no deposits, loans or live-market liquidity.
- Hashi is designed to support Bitcoin-backed finance on Sui.
- The Foundation reports more than 20 day-one launch partners.
- The $500 million figure and its basis are not confirmed in the Foundation’s announcement.
- Hashi’s disclosed collateral design requires signatures from validators and a guardian.
- A live testnet is not evidence of an operating lending market.
What Hashi is designed to do
The Sui Foundation describes Hashi as infrastructure for using Bitcoin as collateral in lending, borrowing, credit markets and other financial products on Sui. These are planned uses. The Foundation’s testnet announcement does not show that the products are already operating at scale. The project aims to enable Bitcoin-backed finance on Sui.
The announcement says Bitcoin collateral is held as unspent transaction outputs, or UTXOs, the individual units of Bitcoin recorded on the network. It describes a 2-of-2 multisignature setup. A transaction needs one signature from Hashi validators, produced using multi-party computation (MPC), and another from a guardian.
Put simply, both sides must approve a transaction before collateral can move. MPC is a cryptographic method that lets participants produce a signature together without bringing their key shares together in one place. The Foundation says the guardian adds another layer of protection by monitoring collateral movements and large transactions. Configurable controls are intended to slow or stop suspicious activity.
These are the project’s descriptions of its design, not an independent security assessment. The announcement does not fully explain who operates the guardian, how independent it is from the validators, what happens if a required signer is compromised or unavailable, or how recovery and redemption work. Requiring two signatures can reduce reliance on one signer, but technical, operational and coordination risks remain.
The July announcement also does not name the Bitcoin-linked asset as “hBTC” or explain a mint-and-burn process. Those details, along with the specific custody and redemption arrangements, need separate documentation before they can be treated as established facts.
What the partner count shows and does not show
The Foundation says more than 20 day-one launch partners had committed to building and deploying capital on Hashi when it announced the devnet earlier in 2026. A devnet is a development network for building and testing software. A testnet gives developers another environment to try integrations and workflows before a mainnet launch.
The Foundation’s partner roster includes organizations such as BitGo, Blockdaemon, Cobo, Ledger, Bullish, FalconX, AlphaLend, Bluefin, Scallop, Suilend, Navi, Certora and OtterSec, among others. They work across custody and wallet infrastructure, lending, DeFi, asset management, oracles, insurance and security.
The partner count signals interest from several parts of the crypto industry, but it does not show that every partner made the same commitment or deposited funds. Building, depositing capital, issuing loans and providing liquidity to users are different measures.
The $500 million figure needs the same scrutiny. The Foundation’s July 22 announcement gives no dollar amount and reports no deposits, outstanding loans or available liquidity. That announcement does not establish the figure’s original source or whether it refers to pledges, allocated capital or funds already deployed.
The post also does not confirm an October 8 update, a phased mainnet rollout later in October, or Anchorage Digital’s reported role and access options. Those claims may relate to later announcements, but the July post alone cannot verify them. It also does not establish whether a later rollout has taken place.
Testnet progress is not proof of demand
A live testnet gives developers and prospective partners a place to test software and integrations before mainnet. It marks useful progress, but does not prove production security, active borrowing or sufficient liquidity. The Foundation says builders can prepare ahead of mainnet, but gives no launch date.
Partner logos and pledges can help a new financial network get started. They cannot create lasting demand on their own. Once Hashi is operating, more useful indicators will include deposits, available liquidity, loans outstanding and utilization, and whether those figures hold up over time.
Bitcoin-backed finance on another network may give people more ways to use BTC without selling it. But users and institutions will need clear documentation on how collateral is secured, who can authorize its movement and how redemption works. “Bitcoin-backed” describes the intended collateral. It does not replace a close look at the mechanisms and risks.
Key questions about Hashi
-
What is Hashi designed to do?
It aims to support Bitcoin-backed lending, borrowing and related financial products on Sui. The Foundation’s testnet announcement does not show these markets operating at scale.
-
What does the Foundation say about its partners?
It reports more than 20 day-one partners committed to building and deploying capital. That does not mean all partners made equivalent commitments or deposited funds.
-
Is the $500 million figure confirmed?
Not by the Foundation’s July 22, 2026 announcement, which gives no commitment amount. The figure’s provenance and what it measures remain unclear. Sui’s Hashi targets Bitcoin-backed finance with $500 million in commitments, not deposits.
-
Is Hashi live on mainnet?
The Foundation confirmed a live testnet and said builders could prepare for mainnet. Its announcement did not give a mainnet date.
-
How does the disclosed collateral design work?
The Foundation describes a 2-of-2 arrangement that requires signatures from Hashi validators and a guardian. The announcement does not provide a full independent assessment of security or the recovery process.
