Bitcoin stays on the Bitcoin network. The work happens on @SuiNetwork.
Hashi is live on mainnet, and institutions can now access hBTC through Porto, our self-custody wallet. Tri-party settlement in qualified custody at Anchorage Digital Bank follows in early 2027.
Fluid hBTC lending markets are now live on @SuiNetwork 🌊
Lenders can now supply stablecoins and earn yield, and borrowers can access stablecoin liquidity against hBTC without selling their Bitcoin.
Fluid continues to expand across VMs, with its smart contracts rebuilt natively in Move, Sui’s programming language.
Fluid has undergone multiple audits and formal verification by @Certora and @osec_io. Audit reports can be found at: https://t.co/rk1pPiF7W1
Fluid is using @redstone_defi and @PythNetwork oracle infrastructure on the Sui network to secure lenders and borrowers.
The initial set of assets includes USDC and hBTC, while the instance is being integrated by multiple wallets, infra providers, and custodians.
Hashi mainnet is live.
Bitcoin holders can now use their $BTC as collateral to borrow stablecoins and access managed vaults on Sui.
20+ partners are expanding access across custody, trading, and DeFi.
Here’s what’s live and what’s next: 🧵
Sui is now supported on Merkl 💧
Our second non-EVM integration, launching alongside the Hashi mainnet.
Teams building on @SuiNetwork can now stream incentives and yield to their users via Merkl. Users can browse Sui opportunities on the Merkl App and receive their rewards with a Sui wallet.
The first Merkl campaign rewards USDC lending on @0xfluid
A more useful Slush home screen starts today 🏠
Check your balance, see your tokens and collectibles, and see how your investments break down. Buy, swap, send or request right below your balance.
You asked for UI improvements. More on the way.
Update Slush to see.
Human code review doesn’t scale once agents write most of the code. No one can read that much code. So the review has to be automated.
But we’ve already seen agents break the rules they were given. Theoretically agents are capable of changing the tests to make them pass, instead of fixing the code.
Then you need a way to confirm the tests weren’t changed. That’s verifiability. The Claude Code team is already doing it this way. Agents write the code, and then it has to pass checks the agents can’t change.
Now, this is only code. Soon agents will be involved in many other kinds of workflows, some of them spanning multiple companies and trust domains.
At that point, verifiability will need credibly neutral infrastructure.