The Voting Escrow contract for PADEX coin.
Initializes the contract with the denom of the PADEX token.
{
"lock_denom": "factory/paloma...",
}CW20 receive msg.
{
"receive": {
"sender": "paloma...",
"amount": "123",
"msg": "<base64_encoded_json_string>"
}
}Lock PADEX and get VePADEX with end lock timestamp.
{
"create_lock": {
"end_lock_time": 10000
}
}Lock more PADEX and get VePADEX.
{
"increase_lock_amount": {
}
}Withdraw locked PADEX
{
"withdraw": {
}
}All query messages are described below. A custom struct is defined for each query response.
Returns the vesting token contract address (the PADEX token address).
{
"config": {}
}The Palomadex Incentives contract allocates token rewards for various Paloma tokens or LP tokens and distributes them pro-rata to LP stakers. We support both cw20 and native Paloma tokens or LP tokens. One more improvement is that PADEX emissions are counted by seconds instead of blocks which makes more sense since Palomadex is multichain protocol.
Contract supports following execute endpoints:
setup_pools- is meant to be called either by owner or generator controller. Reset previous active pools and set new alloc points.deposit- stake Paloma tokens or LP tokens in the generator in order to receive rewards. Rewards are updated and withdrawn automatically. All pools registered the Palomadex factory are stakable. However, it doesn't mean that the pool is incentivized.withdraw- withdraw part or all Paloma tokens or LP tokens from the generator. Rewards are updated and withdrawn automatically.claim_rewards- update and withdraw all rewards associated with the Paloma tokens or LP tokens. This endpoint accepts multiple Paloma tokens or LP tokens.set_tokens_per_second- set new number of PADEX emissions per second. Only owner can call this endpoint.incentivize- add new reward schedule to a specific pool. All overlapped schedules are thoroughly considered and summed up. This is permissonless endpoint. However, it requires to pay incentivization fee in case this reward is new.remove_reward_from_pool- completely remove reward from pool. However, all accrued rewards will be considered at current point. This endpoint can be called only by owner. One must supply remaining rewards receiver address.update_config- is meant to update general contract settings. Only owner can call this endpoint.update_blocked_tokens_list- update list of tokens that are not allowed to be incentivized with PADEX as well as can't be used as external rewards. Only owner can call this endpoint.deactivate_pool- only factory can call this endpoint. Called from deregistration context in factory.propose_new_owner,drop_ownership_proposal,claim_ownership- endpoints to change ownership. Only current owner can propose new owner or drop proposal and only proposed owner can claim ownership.
Anyone can deposit either through direct deposit call with native Paloma tokens or LP tokens supplied or via cw20 send hook.
Contract checks if LP token corresponds to a pair registered in factory. Any LP token is stakable by default although it doesn't mean that it is incentivized in generator.
Partially or fully withdraw Paloma tokens or LP tokens from the generator. Rewards are updated and withdrawn automatically.
Add new reward schedule to a specific pool. All overlapped schedules are thoroughly considered and summed up. This is permissonless endpoint. However, it requires to pay incentivization fee in case this reward is new. Reward schedules are counted by periods where period is one week. Each period starts on Monday 00:00 UTC and ends on Sunday 23:59 UTC. New reward schedule always starts right away and lasts till the next Monday + X weeks, where X - number of weeks specified in the schedule.
This is internal logic which is launched whenever Paloma tokens or LP tokens amount changes, new reward schedule is added or rewards are claimed. Each time update_rewards is called, accrued rewards / total LP staked value is added to the current reward index. rps - rewards per second