Now that we have the jackpot there and the rate is at around 50%, it seems to be consistently disrupting the tests.
I've added a test for the jackpot in the unit tests, so we can be certain the logic is correct when deploying in production. I'm thinking what we need now is to deploy and use a dummy jackpot manager like we had in the old incentive-layer repo.
We can differentiate which one to use at runtime with the production one being deployed like so:
NODE_ENV='production' npm run deploy
Work items:
Move forced error algo to jackpot manager
Create dummy jackpot manager
Integrate dummy jackpot manager into incentive layer contract
Create condition in deploy.js to deploy production jackpot manager when prod
Now that we have the jackpot there and the rate is at around 50%, it seems to be consistently disrupting the tests.
I've added a test for the jackpot in the unit tests, so we can be certain the logic is correct when deploying in production. I'm thinking what we need now is to deploy and use a dummy jackpot manager like we had in the old incentive-layer repo.
We can differentiate which one to use at runtime with the production one being deployed like so:
Work items: