Hashi Is Bringing $500 Million in Bitcoin Finance Commitments to Sui

Sui Foundation says Hashi will enter a phased mainnet rollout later in October with more than $500 million in partner commitments. That figure is an unverified aggregate of commitments—not funded TVL, deposits, deployed BTC, available stablecoin liquidity or originated loans—and its composition and terms remain undisclosed.

Sui has not provided a partner-by-partner breakdown, said whether commitments are binding, distinguished BTC from stablecoin allocations, or supplied deployment deadlines, proof of funds or withdrawal conditions. The headline therefore measures announced intent, not a functioning credit market.

That distinction matters because companies can hold Bitcoin as a long-term treasury asset while needing dollars for payroll, equipment, acquisitions or debt service. Financing operations without selling BTC requires more than a token representation: dependable custody, willing stablecoin lenders, enforceable collateral controls and a route back to native Bitcoin.

The October 8 announcement says Hashi’s rollout will begin later this month, not that the full system is operating. A publication-time check on October 12 found that Sui’s official Hashi documentation still describes the protocol as live on testnet. The official TypeScript SDK documentation says no mainnet deployment exists and that a mainnet client call will fail until one lands.

Hashi was introduced on March 19, its testnet launched on July 22, and the phased mainnet plan was announced October 8. The next milestone should be operational: official mainnet package and object IDs, a working production interface, disclosed participant eligibility and limits, and observable transactions showing BTC deposits, hBTC minting, burns and native-BTC redemptions. Contract deployment alone would not satisfy that test.

The underlying asset does not move onto Sui. A depositor sends BTC to Hashi-managed Bitcoin addresses, where it remains recorded as UTXOs on the Bitcoin blockchain. But “remaining on Bitcoin” does not mean retaining unilateral custody: while collateral is inside Hashi, control shifts to addresses governed jointly through its authorization system.

Once a deposit receives the required Bitcoin confirmations and passes Hashi’s processing checks, the system mints hBTC on Sui against it. That asset can enter lending applications or other financial workflows. To exit, the holder burns hBTC, specifies a Bitcoin destination address, and relies on Hashi’s authorization process to approve, sign and broadcast the native-BTC release.

Consider a hypothetical treasury company holding $20 million of BTC and seeking $5 million of six-month operating liquidity. It could deposit enough BTC into Hashi, receive hBTC and place it into a lending application funded by stablecoin suppliers. At an illustrative 40% initial loan-to-value ratio, it would need at least $12.5 million of collateral before fees, buffers and price movements. Those figures are examples, not announced Hashi terms.

The finance team would still need to assess interest, origination costs, collateral monitoring and the effects of a falling Bitcoin price. Crossing the lender’s maintenance threshold might require more collateral or partial repayment. Otherwise, the BTC position could face liquidation, with execution quality depending on buyers, market depth and application rules.

A successful path ends with the company repaying principal and interest, recovering its hBTC, burning it through Hashi and receiving BTC at its specified address. Every transition matters. A cheap loan with unreliable redemption is not useful treasury financing; neither is reliable custody paired with thin stablecoin liquidity or liquidation machinery that fails during volatility.

Throughput and deployment are therefore secondary to market structure. A usable Bitcoin credit market needs borrowers, stablecoin lenders, custody and collateral operators, benchmark pricing, continuous monitoring, liquidation executors, secondary liquidity and applications that package those elements into understandable products. Announced support does not equal completed integration, enabled client access, deposited capital or measurable production activity.

CF Benchmarks is expected to provide Bitcoin reference-rate data for valuation and risk workflows, including real-time and fixed daily benchmarks delivered to Sui. That can give builders a common input for collateral valuation, reporting and margin processes. It does not determine application-level controls: who monitors collateral ratios, when margin calls occur, which prices trigger liquidation and who executes sales still require confirmation from each lender or vault.

Anchorage Digital adds two institution-facing routes, but the entities must remain distinct. Qualified custody is provided by Anchorage Digital Bank. Atlas collateral-management services come from Anchorage Innovations, while Porto is an unhosted self-custody wallet also provided by Anchorage Innovations—not a qualified-custody product.

In its first-party Hashi announcement, Anchorage says the planned Atlas route is intended to let assets remain in qualified custody while being mobilized as collateral. That could matter for treasury companies, but Hashi-specific settlement and enforcement remain undisclosed: which party controls pledged BTC, how Hashi authorization interacts with the custodian, and how a lender can enforce liquidation without delay or legal ambiguity.

The broader coalition covers necessary market functions rather than one finished product. BitGo and Ledger can provide custody or wallet access; Bullish, Cumberland and FalconX can support trading or liquidity; and Aftermath, Concrete and Fluid can build lending or vault applications. Those relationships should count as active integrations only when client access is confirmed or production activity becomes observable.

Hashi’s security design uses joint withdrawal authorization, threshold signing and a Guardian control that can constrain suspicious outflows. These layers can reduce single-party control and add withdrawal checks, but audits, formal verification and layered authorization do not eliminate custody, oracle, smart-contract, liquidity or liquidation risk.

The adoption test begins after contracts go live: how much BTC becomes active collateral, how much stablecoin credit is originated, what borrowers pay, whether they return for another loan, how deep secondary liquidity becomes, whether liquidations work as designed and whether redemptions complete reliably. Until those figures appear, $500 million remains prospective support, not evidence that Bitcoin-backed credit on Sui is an operational market.