
Summary
Hashi has launched its mainnet with more than 20 custody, retail, and DeFi participants, creating a new infrastructure layer for Bitcoin-related applications on Sui. The system keeps Bitcoin on the Bitcoin network while issuing 1:1 Bitcoin-backed hBTC on Sui for use in lending and other on-chain financial products.
A mainnet launch focused on Bitcoin’s role in Sui finance
Hashi has launched its mainnet as infrastructure designed to connect Bitcoin with financial applications on Sui. According to the Chainwire announcement published by Decrypt, the network now includes more than 20 participants spanning custody, retail access, and decentralized finance. The latest additions identified in the announcement are Merkl, an on-chain incentives platform, and Current, a lending protocol.
The central design does not move native Bitcoin directly onto Sui. Instead, Bitcoin remains on the Bitcoin network while Hashi mints hBTC on Sui as a 1:1 Bitcoin-backed asset. That representation can then be used by Sui-based protocols as collateral for lending, borrowing, and other on-chain financial products. For Sui, the arrangement creates a route for bringing a major external asset into its application ecosystem. For Bitcoin-related finance, it provides access to Sui’s smart-contract environment without requiring Bitcoin itself to natively execute those applications.
The launch therefore represents more than the release of a single token. It introduces a network in which custody providers, validators, trading and access platforms, and DeFi protocols have to work together. The practical value of that network will depend not only on whether hBTC can be issued, but also on whether users and institutions can verify the underlying Bitcoin, understand the control structure, and rely on the system during periods of operational or market stress.
Custody is a central part of the model
Hashi describes itself as decentralized infrastructure secured by validators rather than a single entity, with cryptographic mechanisms supporting the system. That architecture places the validator layer alongside the custody layer as a key part of the trust model. The system must coordinate the underlying Bitcoin, the issuance of hBTC, the verification of relevant states, and the use of that asset within Sui applications.
The announcement names Anchorage Digital, Fluid, HoneyB, and Upshift among the participants supporting access to Bitcoin on Sui. It also says that BitGo is expected to follow in 2027. The listed participants may have different functions, client bases, governance arrangements, and risk controls. Participation in the ecosystem should therefore not be read as evidence that every provider has the same responsibilities or offers the same protections.
For institutional wallet and custody operations, the distinction between native Bitcoin, Bitcoin held in custody, and hBTC issued on Sui is material. A custody team would need to maintain clear records of asset ownership, permissions, transaction approvals, and the relationship between reserves and issued tokens. It would also need to understand who can authorize minting or redemption, how exceptional events are handled, and whether any party has the ability to pause or alter relevant processes.
These questions are common to tokenized and cross-chain financial infrastructure, but they become especially important when a representation of Bitcoin is used as collateral. If a participant cannot access the underlying Bitcoin, if redemption is delayed, or if a validator or smart contract fails, the resulting exposure may extend beyond a simple transaction error. It can affect collateral valuation, lending positions, liquidity, and the ability of other protocols to settle obligations.
New DeFi participants expand the possible use cases
The composition of Hashi’s announced ecosystem points to an attempt to build several layers at once. Custody and access providers help connect users and institutions to the asset. An incentives platform such as Merkl can support the coordination of on-chain participation. Current, identified as a lending protocol, gives hBTC a potential role in credit markets on Sui.
The announcement does not provide detailed information about incentive structures, interest rates, collateral ratios, liquidity levels, or user activity. As a result, the presence of these participants demonstrates ecosystem support but does not establish the scale or commercial performance of any particular application. It also does not remove the need for users and institutions to evaluate each protocol separately.
For hBTC to function effectively as collateral, several conditions would have to hold. Market participants would need reliable information about the relationship between issued tokens and Bitcoin reserves. Sui-based markets would need sufficient liquidity and clearly defined liquidation mechanisms. Protocols would also need procedures for handling failures involving a custodian, validator set, minting system, or underlying blockchain.
Cross-chain and tokenized assets distribute risk across multiple layers rather than eliminating it. A user may face custody risk, smart-contract risk, validator risk, market-liquidity risk, and operational risk at the same time. The more applications that use the same collateral asset, the more important it becomes to understand how stress in one part of the network could affect other protocols.
What the launch means for Sui and Bitcoin finance
Sui gains a pathway for building lending and other DeFi applications around Bitcoin without requiring the Bitcoin network itself to provide the full smart-contract environment for those products. This could broaden the asset base available to Sui protocols and make Bitcoin-related collateral part of a wider application ecosystem.
For Bitcoin finance, the model reflects a continuing effort to place Bitcoin into programmable environments while retaining the underlying asset on its native network. However, “Bitcoin-native finance” should not be treated as synonymous with the security properties of the Bitcoin blockchain alone. hBTC operates on Sui, and its effective security depends on custody arrangements, validators, smart contracts, redemption rules, and the service providers that connect those components.
That distinction matters for institutional users. Due diligence would need to cover more than proof that Bitcoin exists somewhere in reserve. It would also need to examine who controls the reserve, how assets are segregated, what verification or reporting is available, how redemption works, and what happens during technical outages or disputes. Institutional wallet infrastructure may also need separate policy treatment for native Bitcoin and blockchain representations of Bitcoin, including different approval, monitoring, and accounting workflows.
The mainnet begins the operating test
A mainnet launch marks a transition from design and ecosystem formation to live operation. It does not, by itself, demonstrate that a system has passed long-term stress tests or that every participant carries the same risk. The next stage will provide more information about how the network performs in practice.
Key areas to watch include the growth and diversity of the custody set, the transparency of reserve and redemption processes, the distribution and operation of validators, and the response of connected applications to periods of market or technical stress. The role of BitGo, described in the announcement as expected to follow in 2027, will also be relevant to the evolution of the custody network, although the announcement does not provide further details about the scope of that expected support.
Hashi’s launch illustrates a broader shift in Bitcoin-related infrastructure. The focus is moving from simply representing an asset on another chain toward building multi-layer systems that combine custody, verification, access, and financial applications. That structure can expand the range of possible uses, but it also makes transparency and risk separation more important.
For Sui, Hashi offers a new route to Bitcoin-linked DeFi. For institutions, it presents another infrastructure model to assess rather than a substitute for custody and operational due diligence. Whether the network develops into durable financial infrastructure will depend on the reliability of its participants, the clarity of its controls, the verifiability of its backing, and the resilience of the applications built on top of it.
Source: link