π Unveiling Hipo Version 2 Feature: Retired Driver πLet's dive into another transformative feature of Hipo Version 2: Retired Driver.
π Understanding the Driver in v1In Hipo v1, the Driver, a centralized service, played a crucial role. It constantly monitored Hipo's state and triggered actions, like converting hTON into TON when users unstake. Even though this driver is needed in v1, it's still a permission-less protocol, and anyone can trigger these actions by sending messages to the protocol.
π No More Centralized Driver in v2Enter Hipo v2. Thanks to the introduction of
Soul-Bound Tokens (SBTs), the need for the centralized Driver is retired. SBTs seamlessly connect and automate the fulfillment of users' requests.
π How It WorksAs each staking round concludes, SBTs are automatically burned, ensuring the completion of users' requests. This automation not only eliminates the need for a centralized Driver but also contributes to a more decentralized protocol.
π Decentralization at Its CoreBy removing the reliance on a centralized service, Hipo Version 2 aligns more closely with its permission-less ethos. The protocol becomes leaner, more efficient, and truly decentralized.
π Stay tuned for more exciting updates as we continue to unveil the features of Hipo Version 2.