Hashi Targets October Mainnet on Sui

Sui announced on October 8, 2026 that Hashi mainnet is planned to launch later in October. The company said the rollout is backed by more than $500 million in capital commitments from a launch coalition of more than 20 partners. Sui also named Anchorage Digital as a day-one launch partner. The announcement describes a planned launch, rather than confirming that Hashi mainnet is already live.

Hashi is intended to coordinate the use of native Bitcoin as collateral through smart contracts on Sui, according to the issuer. Sui said BTC would remain on the Bitcoin network when it enters the system. In return, hBTC would be minted on Sui against deposited Bitcoin and could be used across applications. When a user exits, the stated process is to burn hBTC and release native BTC back to the Bitcoin network.

That structure separates Bitcoin collateral from its Sui-based representation. hBTC is described as the asset used in Sui applications, while the corresponding BTC remains on Bitcoin under the Hashi collateral arrangement. This means the planned workflow is not a move of Bitcoin’s native settlement layer to Sui. It is a collateral model connecting deposited BTC with programmable use on the Sui network.

Sui said access would open progressively as launch partners complete integrations and enable services for their own clients. A mainnet launch, therefore, would not automatically establish access through every custody provider, wallet, vault, or financial application. The availability of a particular route remains tied to the relevant partner’s integration. Readers should distinguish the announced network timeline from confirmation that a specific service is ready to use.

What the planned rollout includes

The more than $500 million figure refers to capital commitments stated by Sui, not a disclosed measurement of capital already deployed on Hashi mainnet. Sui said the commitments could give Bitcoin-backed markets and vaults a starting base as lending, borrowing, credit, structured products, and other applications are developed. The issuer identified vault providers including Aftermath, Concrete, and Fluid. However, the announcement does not state current vault balances, available borrowing capacity, or terms for any individual product.

Sui described Hashi as an infrastructure primitive rather than a financial product. Under that model, the underlying framework was developed by Mysten Labs, the original contributor to Sui, while financial products are to be independently created and offered by third parties. This distinction matters because the Hashi network framework, a custody route, a vault provider, and a lending or financing offering may involve separate organizations. The announcement does not make every third-party product part of the Hashi infrastructure itself.

Anchorage Digital is expected to provide two routes for its institutional clients, according to Sui. One route is tri-party collateral through Atlas, Anchorage Digital’s settlement and tri-party collateral infrastructure. Sui presented that route for institutions with qualified-custody, compliance, and operational requirements. The company specifically referenced publicly traded companies and digital asset treasury companies among organizations that may face limits on direct DeFi access.

The second stated Anchorage route is self-service access through Porto, its institutional self-custody wallet. Sui said Porto is intended to let institutions access Hashi directly through self-custody and pursue a broader range of strategies across lending, diversified yield, and real-world asset exposure. Sui also said Anchorage Digital plans to provide stablecoin liquidity to Hashi. These are planned partner capabilities, subject to the sequenced rollout and completion of the applicable integrations.

The issuer also outlined the collateral controls it says Hashi uses. BTC collateral is described as secured by a 2-of-2 multisig arrangement requiring authorization from Hashi validators and the guardian. Sui said its Guardian Layer provides an additional check before BTC leaves the system and can slow or stop suspicious collateral movement. The company further stated that Hashi smart contracts underwent formal verification from Certora and that CommonPrefix reviewed the cryptographic security of its MPC protocol.

What to watch as partner access opens

The immediate issue is the difference between a scheduled mainnet launch and broad service availability. Sui’s October 8 announcement said Hashi would go live later that month, but it also described a sequenced release. Access is expected to expand as partners finish their own integrations. A user or institution would need confirmation from the relevant provider before treating a custody route, wallet connection, or application as available.

The stated BTC and hBTC mechanics are another practical point to follow. Sui’s description requires BTC to be deposited before hBTC is minted on Sui. The reverse process requires hBTC to be burned before native BTC is released back to Bitcoin. Anyone assessing the announced system should understand that both the Bitcoin-side collateral process and the Sui-side hBTC use are parts of the same described workflow.

Capital commitments should also be read in their stated context. Sui said its coalition has committed more than $500 million, and that this backing could support Bitcoin-backed markets and vaults as the network rolls out. A commitment does not by itself show how much capital is active in a particular vault or market. It also does not establish liquidity, financing availability, product conditions, or returns for a participant.

The partner lineup signals the intended institutional focus of the launch, but it does not remove the phased-access condition. Sui said more than 20 partners have joined the ecosystem, including custodians, liquidity providers, wallets, infrastructure companies, and DeFi protocols. Anchorage Digital’s announced participation adds Atlas and Porto as planned client routes. Whether either route is usable at a given time depends on the announced integration sequence.

Finally, the security design described by Sui is relevant to the planned collateral model. The issuer says validator and guardian authorization are both required in the 2-of-2 multisig structure, while the Guardian Layer can intervene around suspicious collateral movement. These controls describe the framework Sui says will protect BTC collateral. They should not be confused with confirmation that every future third-party application, vault, or access channel has launched.

• Treat the later-October 2026 mainnet date as a Sui-announced plan, not confirmation that Hashi is already operating.
• Separate more than $500 million in stated capital commitments from deployed liquidity, vault balances, or available financing.
• Follow the stated BTC-to-hBTC process: deposited BTC remains on Bitcoin while hBTC is minted for use on Sui.
• Expect access to depend on individual partner integrations because Sui described the rollout as progressive.
• Review the stated validator-and-guardian authorization structure as part of the planned BTC collateral workflow.

Эта статья носит информационный характер и не является инвестиционной рекомендацией.

admin_wcContributor · World-CryptMore from