SIP-00XX: Optimize Spice Earning by Depositing 20% of SOV on Segment Finance
Background:
Following the approval of SIP-0079, the Adoption Fund’s SOV is staked to harvest BOB’s Spice Points, with an option to renew staking every two weeks. The rewards generated by this strategy should be used to incentivize users to provide liquidity on Sovryn’s AMMs on BOB.
Pursuant to the partnership announcement of May 13th Segment Finance deployed a money market for SOV enabling it to lend SOV and to earn boosted Spice Points on it.
Description:
During the BOB’s Fusion 2 Sovryn could already harvest around 1.2B Spice with the staked 13,8M SOV. The average Value of deposited SOV was around 22M $USD. In the same time period Segment Finance could generate for its users 1.9B Spice having only around 2,2M $USD as TVL value - so basically 15 times more spice per $ than the Adoption Fund’s SOV. Responsible for this over-proportional result was mostly the extra amount of Spice Segment had earned for its extraordinary user activity.
This SIP proposes that 20% of the Adoption Fund’s SOV totalling of 3,864,000 SOV be transferred (lend) into the Segment Finance Contract, creating an opportunity for Sovryn to receive over-proportional spice earning. Assuming a constant spice distribution, the average spice earnings rate can be more than tripled this way, compared to the current status.
The deposit should remain there for the duration of 2 weeks with an option to renew every two weeks and if applicable to increase the staking amount. In case Sovryn governance decides to not to extend the lending period, the SOV will be withdrawn and returned to the Adoption Fund immediately. The harvested Spice amount on Segment Finance is distributed daily, the earning results can be tracked both on the BOB’s and Segment’s dashboard.
Risks:
Like every other DeFi platform, Segment Finance involves smart contract risks.
However, according to Defillama Segment Finance is currently the 3rd biggest protocol on BOB, 30% of the BOB’s users are interacting with Segment on a daily basis. The protocol utilizes the battle tested codebase of Compound V2 and has gone through multiple audits. On top of that, Segment has an active bug bounty program on Immunefi and an active security monitoring system. Apart from the external solutions, protocol operations are being managed through a multisig wallet with a 48 hours timelock.
The risk is also mitigated by the fact that the SOV deposited into the Segment’s Contract will be SOV bridged to Ethereum (eSOV) and in the event of a loss of funds, the assets can be black listed and the original SOV (on Rootstock) will not be affected.
Proposed Changes:
Transfer (Lend) a total of 3,864,000 SOV from the Sovryn contract on BOB (0xc17c6462ceafe9a8819258c6ba168bef5544fc21) to the Segment Finance SOV contract (0x2136EbC7Be1E65fDB4A407Ac2874b3d6850A64c2)
License
Copyright and related rights waived via CC0.