-
Notifications
You must be signed in to change notification settings - Fork 700
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider removing suppressed and submitted_in from Nominations #332
Comments
I'd like to work on this. Anything special to consider? |
This is just a migration (if any at all) and very small code changes, and the PR that is blocking it might not get merged anytime soon, so I'd recommend waiting on it. |
Ah, nevermind. I missed that paritytech/substrate#8197 was unmerged. |
Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. |
meh, should stay around for now. |
* Fix rococo-runtime naming clash * Use wasm in benchmarks * Add frame_system weights & benchmark wasm
* Move associated type to pallet evm * wire it into the evm backend * Fix test mocks
Ironically, this will be needed for polkadot-fellows/RFCs#86 which is getting good traction. |
If paritytech/substrate#8197 gets merged, or generally we get full slash reversal, we no longer use neither
submitted_in
norsuppressed
if theNomination
struct inpallet-staking
. Consider removing these in favour of state-space.The text was updated successfully, but these errors were encountered: