Stargate V2 proposal has been approved by the community vote, which will introduce transaction batching and dynamic credit allocation

The Snapshot page shows that the Stargate V2 proposal passed the Stargate community vote with a support rate of 95.57%. According to the proposal, Stargate V2 will introduce transaction batching and dynamic credit allocation (managed by the AI ​​planning module) to improve cross-chain efficiency and reduce cross-chain cost. Additionally, Hydra was introduced as an extension of Stargate in the area of ​​Bridging as a Service, which allows new chains to access unlimited liquidity on all Stargate chains. Upon DAO approval, the Stargate V2 protocol will be launched according to the following execution plan: - Incentives on Stargate V1 pools should be gradually reduced, eventually dropping to 0 after X period of time; these pools must remain active for migrate. -The Stargate V2 protocol should be deployed on all DAO-approved chains with relevant assets attached. The list of these chains can be found in Appendix 2; compared to V1, this list has two significant changes: a. All chains that have recently deployed native USDC tokens (such as Arbitrum, Optimism, Polygon, Base) will support this A native token rather than the bridged USDC.e token. b.Klaytn will be the first supported Hydra chain, and future Hydra chains will be deployed in coordination with the Stargate Foundation. - Within 48 hours before the scheduled launch date/time, Stargate shall open the V2 liquidity pool for deposits and increase incentives prior to launch. -The first version of the AI ​​planning module has been built. With the launch of V2, the AI ​​module will be trained based on Stargate's rolling data in the previous period to optimize the following two aspects: a. Stargate should always be the cheapest bridging tool, b. Stargate should maximize its protocol revenue. -Additional fees on Stargate V2 will continue to be attributed to the protocol/DAO as POL. -Stargate should deploy its own DVN managed by the Foundation and use it as a required signer for every Stargate message; Stargate should also use the Nethermind DVN for additional security verification.