• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
SaddleSaddleby0xb44f710054AABE793A14125646BadFD43791a5c4lowpolyduck.eth

SIP-14: Deploy Saddle to Kava

Voting ended almost 4 years agoSucceeded

Summary

Deploy Saddle 2pool (USDC + USDT) to Kava testnet and mainnet-- If Frax and Terra agree to provide additional incentives, launch with 4pool instead.

Motivation

Kava is a IBC-enabled blockchain, currently with over $600m in TVL, and with a market cap of over $730m. In May the Kava team will launch a new EVM compatible blockchain, utilizing the same validators as the IBC-enabled chain. As a part of this new EVM-compatible chain, Kava has two programs to incentivize protocol deployments. Saddle stands to gain from a deployment by acquiring:

Our pro-rata share of 100k Kava incentives if Saddle deploys before mainnet launch as a part of Kava’s Pioneer Program, and Our pro-rata share of the $750m developer fund paid out to the top 100 protocols by TVL over 4 years as a part of the Kava Rise program. Discussions with the team have informed us that there are currently no other StableSwap providers planning to deploy to Kava. Furthermore, both rewards will help attract liquidity without the need to emit extra SDL tokens. This provides a unique asymmetric opportunity for Saddle to attract new liquidity with little risk of SDL emissions.

Specification

Deploy Saddle to Kava testnet and mainnet initially with 2pool (USDC + USDT) using the Kava incentives from both the Pioneer and Rise programs to incentivize liquidity. A further governance proposal to deploy SDL emissions on top of Kava incentives may follow pending an assessment of the success of the EVM-compatible Kava blockchain.

For: Deploy Saddle to Kava’s EVM-compatible testnet and mainnet, with 2pool and Kava incentives-- If Frax and Terra agree to provide additional incentives, launch with 4pool instead.

Against: No change.

Off-Chain Vote

For
1.51M SDL71.5%
Against
601.2K SDL28.5%
Download mobile app to vote

Timeline

Apr 22, 2022Proposal created
Apr 23, 2022Proposal vote started
Apr 26, 2022Proposal vote ended
Oct 26, 2023Proposal updated