Generic Staking/Slashing Modules

[AdityaSripal]

Summary

Currently the staking/slashing modules are designed for Tendermint consensus exclusively. However, staking/slashing functionality could be used in a variety of state-machine applications (e.g. dCERT/Oracles). Thus, the staking/slashing modules should be redesigned to allow developers to use staking/slashing for any purpose.

Proposal

• Remove Tendermint consensus specific logic from x/staking and x/slashing
• Define interfaces/types to pass into staking/slashing keepers that will run application-specific logic on slashing/staking state

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[alexanderbez]

@AdityaSripal this issue seems very very broad. It is prudent to first identify all points of tight coupling and dependency on Tendermint (e.g. power ranking) before proceeding. Preferably laid out in this issue before any work is tasked.

/cc @rigelrozanski

[rigelrozanski]

Like the idea. I think what we really need is a generic consensus engine interface (of which tendermint fulfills) which contains expected parameters (for ex. validator delay blocks). This way staking and slashing could operate with any consensus engine which fulfills the sdk consensus engine interface

[zmanian]

This is IMO a very important direction to explore.

I'd also like to at some point enable dynamically loaded slashing/staking related code via web assembly.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.