dexter-multi-staking
| Crates.io | dexter-multi-staking |
| lib.rs | dexter-multi-staking |
| version | 3.0.0 |
| source | src |
| created_at | 2024-03-06 16:48:51.882182 |
| updated_at | 2024-03-06 16:48:51.882182 |
| description | Dexter Multi-Staking Contract: allows to stake LP tokens and earn rewards in multiple tokens |
| homepage | |
| repository | https://github.com/dexter-zone/dexter_core |
| max_upload_size | |
| id | 1164987 |
| size | 242,194 |
Pranjal Paliwal (betterclever)
documentation
README
Dexter - Multi-staking contract
Dexter Multi-staking contract enables LP incentivization mechanism on Dexter. It supports following features:
- Creation of multiple reward schedules which can be overlapping as well.
- Reward schedule assets can be both CW20 and Native tokens.
- 'Bonding' functionality for the users by which they deposit their LP tokens, to be eligible for receiving rewards.
- Reward schedule amount is linearly distributed to the users based on their bonding ratio i.e. their bonded amount : total bonded amount for that LP token.
Roles
Owner: Manages the contract admin parameters. With v2.2 of the Multi-staking contract (v1.1 release of the Dexter Protocol), this role is governed by the Governance Admin contract. Prior to this release, this was managed by a Cosmwasm multi-sig.
Reward Schedule Creator: This type of user creates reward schedules. This user is also elligible to redeem some undistributed rewards if left in the contract. See here.
User: User who bonds / unbonds LP tokens in the contract.
Supported state transition functions
Owner executable
Following transition functions can only be executed by the owner of the contract.
1. Create Reward Schedule
Creates a new reward schedule. Owner can create a reward sFchedule on the behalf of a user.