# Why SailFish ## Native Batch Transaction SailFish is the Liquidity hub for EDUCHAIN. Powering Liquidity for EduFi. ## Super Easy Real-time Voting Traditionally, the voting process was quite complex. You had to grasp the concepts of epochs, voting power, its decay over time, lockup periods, veNFTs, and the intricacies of merging and splitting. Additionally, you needed to calculate how to distribute your voting power across multiple pools using estimated APR and the total value of your voting power—a daunting task to repeat weekly. On SailFish, voting has been simplified to farming with fungible ve tokens. Instead of doing the calculations yourself, you can simply click "smart vote," and we'll handle the rest. ## Smart Split Router With the introduction of native batch transactions, our smart split router works similarly to a DEX aggregator by allowing swaps to take multiple paths, optimally divided by size, rather than following a single route. This approach minimizes price impact. This feature eliminates the need for third-party aggregators, saving on upfront fees and positive slippage while significantly reducing gas costs. ## Fair Fungible Vote Token Protocols with voting escrow (ve) lock tokens typically set the maximum lock period between 1 to 4 years, with voting power granted based on the remaining lock duration. Although earning more shares by locking tokens longer might seem advantageous, this system has several significant drawbacks: * **Designed for Absolute Team Dominance Regardless of Tokenomics** * **Inefficiencies and Inequities Due to Non-Uniform Lock-Ups** * **Inevitable Emergence of Third-Party Wrappers** SailFish rejects these misleading tokenomics by introducing transparent fungible voting tokens. This approach ensures equal lock-up conditions for everyone and allows for immediate and easy liquidation through the SAIL-veSAIL pool. As a result, value circulates safely and entirely within the protocol, eliminating the need for third-party wrapper intervention. ## V3 Liquidity Provision --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://vedex.gitbook.io/docs/getting-started/why-sailfish.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.