We are beginning the safe wind down of the Bitfrost bridge as we focus on our core product: building the infrastructure layer for on-chain perps and prediction markets.
As part of this process, deposits will be disabled and withdrawals will remain enabled. Please withdraw your assets between 05/29/26 to 06/05/26.
Thank you to everyone who has supported the bridge so far. We are grateful for the community around this product and excited for the next leg of the journey together.
We are beginning the safe wind down of the Bitfrost bridge as we focus on our core product: building the infrastructure layer for on-chain perps and prediction markets.
As part of this process, deposits will be disabled and withdrawals will remain enabled. Please withdraw your assets between 05/29/26 to 06/05/26.
Thank you to everyone who has supported the bridge so far. We are grateful for the community around this product and excited for the next leg of the journey together.
The bridge is temporarily not in function because of the recent Zcash binary update, all funds are safe. Please don’t do any transfer till the Zcash binary update. No money send after 05/15/2026 will be processed.
Please do not use the iZEC market on Hyperliquid.
The iZEC market was deployed with an incorrect configuration of the Hyperliquidity parameters. Note that the token is not 1:1 backed by native $ZEC.
We have disabled the bridge to safeguard users.
Next steps:
- We will acquire a new ticker immediately.
- The reimbursement process for traders of this asset will be communicated.
Thanks to @silhouette_ex and @HyperliquidX for working with us on helping to resolve this issue.
Please do not use the iZEC market on Hyperliquid.
The iZEC market was deployed with an incorrect configuration of the Hyperliquidity parameters. Note that the token is not 1:1 backed by native $ZEC.
We have disabled the bridge to safeguard users.
Next steps:
- We will acquire a new ticker immediately.
- The reimbursement process for traders of this asset will be communicated.
Thanks to @silhouette_ex and @HyperliquidX for working with us on helping to resolve this issue.