New staking mechanics: delay on entry opposed to exit
This commit is contained in:
@@ -39,60 +39,9 @@ blockchainTests('Staking & Delegating', env => {
|
||||
await stakingWrapper.deployAndConfigureContractsAsync();
|
||||
});
|
||||
blockchainTests.resets('Staking', () => {
|
||||
it('basic staking/unstaking', async () => {
|
||||
// setup test parameters
|
||||
const amountToStake = StakingWrapper.toBaseUnitAmount(10);
|
||||
const amountToDeactivate = StakingWrapper.toBaseUnitAmount(4);
|
||||
const amountToReactivate = StakingWrapper.toBaseUnitAmount(1);
|
||||
const amountToWithdraw = StakingWrapper.toBaseUnitAmount(1.5);
|
||||
// run test - this actor will validate its own state
|
||||
const staker = new StakerActor(stakers[0], stakingWrapper);
|
||||
await staker.depositZrxAndMintActivatedStakeAsync(amountToStake);
|
||||
await staker.deactivateAndTimeLockStakeAsync(amountToDeactivate);
|
||||
// note - we cannot re-activate this timeLocked stake until at least one full timeLock period has passed.
|
||||
// attempting to do so should revert.
|
||||
const revertError = new StakingRevertErrors.InsufficientBalanceError(amountToReactivate, 0);
|
||||
await staker.activateStakeAsync(amountToReactivate, revertError);
|
||||
await staker.skipToNextTimeLockPeriodAsync();
|
||||
await staker.activateStakeAsync(amountToReactivate, revertError);
|
||||
await staker.skipToNextTimeLockPeriodAsync();
|
||||
// this forces the internal state to update; it is not necessary to activate stake, but
|
||||
// allows us to check that state is updated correctly after a timeLock period rolls over.
|
||||
await staker.forceTimeLockSyncAsync();
|
||||
// now we can activate stake
|
||||
await staker.activateStakeAsync(amountToReactivate);
|
||||
await staker.burnDeactivatedStakeAndWithdrawZrxAsync(amountToWithdraw);
|
||||
});
|
||||
});
|
||||
|
||||
blockchainTests.resets('Delegating', () => {
|
||||
it('basic delegating/undelegating', async () => {
|
||||
// setup test parameters
|
||||
const amountToDelegate = StakingWrapper.toBaseUnitAmount(10);
|
||||
const amountToDeactivate = StakingWrapper.toBaseUnitAmount(4);
|
||||
const amountToReactivate = StakingWrapper.toBaseUnitAmount(1);
|
||||
const amountToWithdraw = StakingWrapper.toBaseUnitAmount(1.5);
|
||||
const poolOperator = stakers[1];
|
||||
const operatorShare = 39;
|
||||
const poolId = await stakingWrapper.createStakingPoolAsync(poolOperator, operatorShare);
|
||||
// run test
|
||||
const delegator = new DelegatorActor(stakers[0], stakingWrapper);
|
||||
await delegator.depositZrxAndDelegateToStakingPoolAsync(poolId, amountToDelegate);
|
||||
await delegator.deactivateAndTimeLockDelegatedStakeAsync(poolId, amountToDeactivate);
|
||||
// note - we cannot re-activate this timeLocked stake until at least one full timeLock period has passed.
|
||||
// attempting to do so should revert.
|
||||
const revertError = new StakingRevertErrors.InsufficientBalanceError(amountToReactivate, 0);
|
||||
await delegator.activateStakeAsync(amountToReactivate, revertError);
|
||||
await delegator.skipToNextTimeLockPeriodAsync();
|
||||
await delegator.activateStakeAsync(amountToReactivate, revertError);
|
||||
await delegator.skipToNextTimeLockPeriodAsync();
|
||||
// this forces the internal state to update; it is not necessary to activate stake, but
|
||||
// allows us to check that state is updated correctly after a timeLock period rolls over.
|
||||
await delegator.forceTimeLockSyncAsync();
|
||||
// now we can activate stake
|
||||
await delegator.activateAndDelegateStakeAsync(poolId, amountToReactivate);
|
||||
await delegator.burnDeactivatedStakeAndWithdrawZrxAsync(amountToWithdraw);
|
||||
});
|
||||
});
|
||||
});
|
||||
// tslint:enable:no-unnecessary-type-assertion
|
||||
|
||||
Reference in New Issue
Block a user