Staking V2: batch operations, precompile validation, and safer staking failures - #5083

Rule: merge rule to main (merge)

• #approved-reviews-by>=2
• #commits-behind = 0 [🛡 GitHub branch protection]
• base=main
• check-success=Travis CI - Pull Request
• github-review-approved [🛡 GitHub branch protection]
• head=dev
• label=ready-to-merge
• #commits-unverified=0
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
• #review-threads-unresolved=0
• -closed [📌 merge requirement]
• -conflict
• -conflict [📌 merge requirement]
• -draft
• -draft [📌 merge requirement]
• -title~=(?i)wip
• check-success=GitGuardian Security Checks
• label!=(?i)wip
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com