Blog By Tags:
Tech Update

We are thrilled to announce our smart contract V2 is now live on Testnet! This update brings in some significant structural changes, including the integration of Debt Shares, the introduction of Dynamic Exchange Fees, a new Liquidation Mechanism, and a fresh Weekly zUSD Fee Distribution system. These changes represent a major milestone in Horizon Protocol’s evolution and have established a strong foundation for the forthcoming launch of the Perpetual Futures Exchange, ensuring enhanced security, stability, and functionality.

We’re excited to share an update alongside our upcoming Testnet V2 smart contract releases. This update focuses on improving the Weekly zUSD fee distribution. The goal is to make this change beneficial for our community of stakers and promote a fairer fee distribution system.

Horizon Protocol is a protocol that requires the maintenance of collateral to make sure that all zAssets are backed by some underlying asset. In the case of Horizon Protocol, that underlying asset is the HZN token. The worst-case scenario is if the underlying asset’s value is worth less than zAssets, because that would mean that zAssets are not completely backed anymore. One of the mechanisms to prevent the worst-case scenario is the liquidation mechanism, which allows wallets that have gone below the safe C-ratio, or collateralization ratio, threshold to be liquidated by a third party to get them back to a safe C-ratio and ensure the protocol’s zAssets are sufficiently collateralized.

We’re excited to introduce Dynamic Exchange Fees, one of the upcoming changes in our Horizon Protocol V2 smart contract testnet.

We’re excited to share some upcoming changes in our Horizon Protocol V2 smart contract testnet. These changes, including Debt Shares, Dynamic Exchange Fees, and a new Liquidation Mechanism, are significant and will enhance the protocol’s stability, scalability, and user experience. They lay the groundwork for the Futures Exchange we have in store.

We’re here to provide you with an update regarding HIP-7 and the Multi-signature (Multisig) process that we previously discussed in our last community call.