Proof of stake tests › Accuracy rewards scenarios
  ✅ User liq. is considered on the ongoing session

Proof of stake tests › Activation rewards scenarios
  ✅ A user can activate some rewards
  ✅ A user can activate twice some rewards
  ✅ A user can activate rewards that were activated on some other schedules

Proof of stake tests › Burn liquidity
  ✅ GIVEN a user with N tokens activated for 3rd party, WHEN the user wants to burn ( all the existing - N ) THEN the operation works

Proof of stake tests › Claim rewards scenarios
  ✅ When rewards not available, should return error
  ✅ Rewards are divided in n-sessions
  ✅ Two users activated, one in one exec, other in two - check balances
  ✅ Rewards are not given for the ongoing session it got scheduled

Proof of stake tests › FeeCosts
  ✅ Reward a pool is not free of cost
  ✅ Activate - deactivate is free if success
  ✅ Activate - deactivate is not free if fails
  ✅ Claiming is not free if Zero

Proof of stake tests › Happy path
  ✅ A user can deactivate all the tokens when partial activation / deactivation

Proof of stake tests › MPL integration
  ✅ User [testUser1] with: stakedUnactivatedReserves ->  stakedAndActivatedReserves -> stakedUnactivatedReserves
  ✅ Bug ? User [testUser2] with: stakedActivatedReserves ->  stakedAndActivatedReserves -> stakedAndActivatedReserves
  ✅ User [testUser3] with: activatedUnstakedReserves ->  activatedUnstakedReserves -> activatedUnstakedReserves
  ✅ User [testUser4] with: unspentReserves ->  activatedUnstakedReserves -> unspentReserves

Proof of stake tests › Activations are reused if new rewards
  ✅ A user can activate - finish schedule and get automatically activated for the following schedules

Proof of stake tests › Setup rewards scenarios
  ✅ Multiple users can reward the same pool - same tokens
  ✅ Multiple users can reward multiple pools - token does not belong to the promoted pool
  ✅ A user can reward a pool that is not directly paired with mgx
  ✅ A user can reward in mgx
  ✅ Rewards schedule must last at least 1 session ahead
  ✅ Min liq is required setup rewards
  ✅ Min liq valuation is required setup rewards

Proof of stake tests › Activation rewards scenarios
  ✅ GIVEN promoted pool MGX-Token2 AND user with liquidity tokens for MGX-Token2 WHEN user tries to activate 3rd party rewards for Token1 THEN receive error
  ✅ GIVEN promoted pool MGX-Token2, pool MGX-Token1 AND user without liquidity tokens for MGX-Token2 WHEN  user tries to activate 3rd party rewards for Token1 THEN receive error
  ✅ GIVEN promoted pool MGX-Token2, pool MGX-Token1 AND user with liquidity tokens for MGX-Token2 WHEN user tries to activate 3rd party rewards for Token1 with too many liquidity tokens THEN receive error
  ✅ GIVEN promoted pool MGX-Token2, pool MGX-Token1 AND user with liquidity tokens for MGX-Token2 WHEN user activates 3rd party rewards for Token1 AND does not uses rewardPool function THEN he cant claim rewards
  ✅ GIVEN promoted pool MGX-Token2, pool MGX-Token1 AND user with liquidity tokens for MGX-Token2 WHEN user activates 3rd party rewards for Token1, waits and claims all rewards THEN operation is successful
  ✅ GIVEN promoted pool MGX-Token2, pool MGX-Token1 AND user with liquidity tokens for MGX-Token2 WHEN user activates 3rd party rewards for Token1, waits more than one period last AND the user burns all his liquidity THEN users can still claim pending rewards
  ✅ GIVEN promoted pool MGX-Token2,  pool MGX-Token1,  pool MGX-Token3 AND user with activated 3rd party rewards of pool MGX-Token2 for Token1 and Token3 WHEN user claim all rewards  THEN he receive 2 type of rewards
  ✅ GIVEN promoted pool MGX-Token2, pool MGX-Token1 AND user with activated 3rd party rewards of pool MGX-Token2 for Token1 WHEN user deactivates 3rd party rewadrs with too many liquidity tokens THEN receive error