KIP-86: Staking V2 Integrator Contract Support

Simple Summary

Staking V2 has been engineered so the community will continue receiving rewards for their V1 locked escrow.

However, in order for this intention to be fully fulfilled, Staking V2 also needs to support Staking V1 contract stakers (community members who staked their escrow via a smart contract).

This KIP ensures that individuals who staked in V1 via contract will also be rewarded in V2 for their locked V1 stake.

Abstract

This change will add a new interface and functions that allow community members to claim V2 rewards for their V1 locked escrow.

This will allow integrators and any other community member who has staked via a contract to claim their V2 rewards in the same way EOA stakers can.

Motivation

The decision was made when designing Staking V2 that we should do the best possible within engineering constraints to ensure that no users unfairly lose rewards due to the migration.

Hence Staking V2 was designed to provide rewards for funds locked in immutable V1 contracts that cannot be migrated.

The system is already engineered to support this for EOAs, but without this change, users who have staked via smart contract will miss out.

This KIP will ensure everyone in the community is treated equally.

Specification

For more information, visit the: Kwenta State Log