Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] - RG Token for SKILL in Revenue Share Pool #1838

Open
3 tasks done
remocwenn opened this issue Dec 19, 2022 · 0 comments
Open
3 tasks done

[Feature] - RG Token for SKILL in Revenue Share Pool #1838

remocwenn opened this issue Dec 19, 2022 · 0 comments

Comments

@remocwenn
Copy link

Prerequisites

  • I checked to make sure that this feature has not already been filed
  • I'm reporting this information to the correct repository
  • I understand enough about this issue to complete a comprehensive document

Describe the feature and its requirements

The revenue share pool distribution related to the amount of RG tokens held. In order to unstake SKILL from the revenue share pool, they must submit RG tokens in a 1:1 ratio.

  • Users should be able to unstake SKILL from this pool by submitting RG tokens in a 1:1 ratio
    • Meaning the only way users should be able to remove SKILL from this pool is by submitting the equivalent amount of RG tokens
    • RG token address: 0x04D686c53b27eca52a8F15C51D94Ba346540BdE2
    • Example: Joe wants to unstake his 150 SKILL in the revenue share pool. He must submit 150 RG tokens and in return, he obtains his 150 SKILL
    • The amount of RG tokens submitted should be able to be selected so it is not a 0 or maximum amount problem. In the example above, Joe would be able to submit anywhere between 0 and 150 RG tokens for that equivalent amount of SKILL.
  • Users should still be able to claim any SKILL rewards from this pool

image

Is your feature request related to an existing issue? Please describe.

Yes - [Feature] - Close Revenue Share Pool #1837

  • 1837 should be completed prior to starting this issue

Is there anything stopping this feature being completed?

No

Describe alternatives you've considered

N/A

Additional context

N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant