✨ New evaluation reward/slash thresholds

[JuaniRios]

What?

• There is now only one threshold configurable at runtime. Above the project is successful and evaluators rewarded, below project fails and evaluators slashed. No issuer decision

Why?

• Simplifies logic greatly

Testing?

• Commented out all tests for now. Will be fixed in a later PR

[JuaniRios]

• 💿 AWS runtime weight generation #376 : 3 dependent PRs (#375 , #379 , #380 )
• 🛠️ Rework benchmarks #374
• 💥 Remove AuctionInitializePeriod #377
• ✅ New tests #372
• ✨ Add mark project settled extrinsic #373
• 💥 Remove random end field #371
• 💥 Remove AuctionClosingDuration #369
• ✌️ Fix project transition event #368
• 🛠️ Rework tests #365
• 🗑️ Remove unnecessary bid fields #367
• ✨ New evaluation reward/slash thresholds #366 👈
• 🐛 Fix Compilation #364 : 1 other dependent PR (#370 )
• 🚮 Remove "Y" variable from fee allocation #363
• ✲ Transitions can be called by anyone #362
• 🧹 Cargo fmt #361
• Vstam1/simplifications #358
• 😎 Runtime APIs #354
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JuaniRios and the rest of your teammates on Graphite

[JuaniRios]

Merge activity

• Aug 23, 5:56 AM EDT: @JuaniRios started a stack merge that includes this pull request via Graphite.
• Aug 23, 6:10 AM EDT: Graphite rebased this pull request as part of a merge.
• Aug 23, 6:11 AM EDT: @JuaniRios merged this pull request with Graphite.