
Summary
Hashi, a Bitcoin finance infrastructure project for the Sui ecosystem, has launched its mainnet with support from more than 20 custody, retail and DeFi participants. The system keeps Bitcoin on the Bitcoin network while issuing 1:1 Bitcoin-backed hBTC on Sui for use in lending, collateral and other onchain applications.
A new bridge between Bitcoin and Sui’s application layer
Hashi has announced the launch of its mainnet, positioning the network as infrastructure for bringing Bitcoin-related financial activity into the Sui ecosystem. According to material distributed by Chainwire and published by Decrypt, more than 20 custody, retail and DeFi participants are supporting the launch. The named participants include Anchorage Digital, Fluid, HoneyB and Upshift, while Merkl and Current were identified as the latest additions. BitGo is expected to follow in 2027, according to the announcement.
The central idea is not to alter Bitcoin’s base network or turn Bitcoin itself into a native Sui asset. Instead, Hashi is designed to keep Bitcoin on the Bitcoin network while creating a corresponding asset on Sui. That asset, known as hBTC, is described as being backed by Bitcoin on a one-to-one basis. Once issued on Sui, hBTC can be used within lending, borrowing and other onchain financial applications.
This reflects a broader infrastructure trend in digital assets: networks with large pools of relatively inactive or less composable capital are being connected to ecosystems that support more complex application logic. In Hashi’s case, Bitcoin is the source asset and Sui is the environment in which developers can build additional financial functions around a representation of that asset.
hBTC is the core piece of the model
The proposed structure depends on maintaining a reliable relationship between native Bitcoin and hBTC. Bitcoin remains on its original network, while the Sui-side asset is minted to represent the corresponding Bitcoin. In principle, this gives Sui applications access to a Bitcoin-linked form of collateral without requiring the Bitcoin network itself to process the application’s lending or other financial logic.
That design creates both utility and a set of operational dependencies. The system must account for the custody of the underlying Bitcoin, the authorization of minting and redemption, the validation of cross-network messages, and the accurate representation of supply on Sui. If any of those processes fail or become opaque, confidence in the one-to-one relationship can be weakened.
The announcement does not provide detailed information on reserve reporting, redemption procedures, collateral parameters, liquidation rules or the operating responsibilities of each participant. Those details will matter as the network moves from a launch announcement to sustained use. A mainnet launch means that the infrastructure is entering live operation; it does not, by itself, establish a long-term record of security, liquidity or resilience.
For Sui developers, hBTC could provide a Bitcoin-linked collateral base for applications that previously relied on assets native to Sui or on other representations of Bitcoin. The potential use cases described in the announcement include lending, borrowing and broader onchain financial products. The practical performance of those products, however, will depend on their own contracts, risk controls, liquidity conditions and governance arrangements.
The participant mix points to a full-stack infrastructure strategy
Hashi’s announced coalition spans more than one segment of the digital-asset market. Custody providers and access platforms are represented alongside DeFi applications and incentive infrastructure. That mix suggests an attempt to assemble a broader operating environment rather than simply issue a cross-chain token and leave application development to third parties.
Anchorage Digital is cited in connection with institutional access, while Fluid, HoneyB and Upshift are listed among the supporting participants. The announcement also says that BitGo is expected to join in 2027. Because the source material does not specify the precise technical or commercial role of each participant, the list should not be read as evidence that every organization performs the same custody, validation, liquidity or distribution function.
Merkl and Current add two distinct application directions. Merkl is described as an onchain incentive platform, while Current is described as a lending protocol. Their participation indicates that the ecosystem is seeking to connect the Bitcoin-linked asset to both incentive mechanisms and credit-related applications. Still, the available announcement does not disclose usage figures, lending volumes, product terms or risk limits. Those omissions make it too early to assess the scale of activity or the durability of demand.
Decentralized validation does not remove trust assumptions
Hashi describes itself as decentralized by design and says it is secured by validators rather than a single entity, using cryptographic mechanisms. Compared with a model controlled by one custodian or one administrative key, a validator-based structure can distribute parts of the system’s security and operational responsibility.
That claim also creates a set of questions that will be relevant to institutional users and developers. Observers will need to understand how validators are selected, whether control is concentrated among a small group, how cross-chain messages are confirmed, and what happens when validators disagree or an abnormal event occurs. The security of the overall system may depend not only on cryptography but also on governance, key management and procedures for pausing or recovering operations.
The custody layer presents another important consideration. Institutional participation can bring established operational processes and compliance capabilities, but it also introduces questions about legal entities, asset segregation, access permissions, service jurisdictions and redemption rights. For institutional wallet and custody teams, supporting a cross-chain asset requires more than adding a new token format. It can involve transaction-policy controls, address management, approval workflows, monitoring of supply and reserves, and response plans for incidents.
In that sense, Hashi is relevant to the institutional custody conversation even though the announcement is primarily about blockchain infrastructure. A Bitcoin-linked asset that becomes usable in DeFi has to be evaluated across several layers at once: the underlying Bitcoin custody arrangement, the bridge or issuance mechanism, the Sui smart contracts, the participating applications and the governance process that coordinates them.
The next test is sustained operation, not the launch announcement
The mainnet launch establishes a connection between Bitcoin and Sui, but it does not by itself demonstrate that a mature market has formed. The ecosystem will need reliable issuance and redemption, transparent information about the underlying reserves, resilient validator operations and applications with clearly defined risk controls. Lending and other financial products also bring application-specific risks that are separate from the security of the underlying cross-chain asset.
Future disclosures will therefore be important. Relevant areas include the frequency and format of reserve verification, the mechanics for creating and redeeming hBTC, the distribution and activity of validators, independent security reviews, the exact responsibilities of participating custodians and the treatment of failures or disputes. Data on actual usage and product performance would also help distinguish ecosystem support from sustained adoption.
Hashi’s launch illustrates how Bitcoin infrastructure is increasingly being framed around composability rather than simple transfer. The question is no longer only whether Bitcoin can be represented on another network, but whether that representation can support financial applications without creating unclear or excessive layers of dependence.
For Sui, the project could add a Bitcoin-linked asset to its developing DeFi environment. For custodians and institutional wallet operators, it highlights the need to combine blockchain connectivity with controls around permissions, reserves, settlement and incident response. For users and developers, the relevant assessment will depend on evidence accumulated after launch rather than on the size of the initial partner list alone.
At this stage, Hashi is best understood as a cross-chain financial infrastructure project entering live operation. Its significance will ultimately be determined by the transparency of its custody and validation model, the security of its contracts, the quality of its participating applications and its ability to manage the risks created when Bitcoin-backed assets are used across networks.
Source: link