Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Westend] Ensure staking election works in absence of a signed solution #3671

Closed
Ank4n opened this issue Mar 12, 2024 · 2 comments
Closed

[Westend] Ensure staking election works in absence of a signed solution #3671

Ank4n opened this issue Mar 12, 2024 · 2 comments
Labels
R0-silent Changes should not be mentioned in any release notes

Comments

@Ank4n
Copy link
Contributor

Ank4n commented Mar 12, 2024

Same as paritytech/polkadot#7193, reopening in light of #3646.

Merklized metadata RFC: polkadot-fellows/RFCs#78

Can we setup OCW that it does not submit solution every once a while?
@Ank4n Ank4n added the R0-silent Changes should not be mentioned in any release notes label Mar 12, 2024
@kianenigma
Copy link
Contributor

I am still in favor of removing this constant from the metadata and removing the parent PR. Based on what I read, it is not used int the metadata.

@bkchr
Copy link
Member

bkchr commented Mar 26, 2024

Removed the constants.

@bkchr bkchr closed this as completed Mar 26, 2024
@github-project-automation github-project-automation bot moved this from 📕 Backlog to ✅ Done in (Nominated) Proof of Stake Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
R0-silent Changes should not be mentioned in any release notes
Projects
(Nominated) Proof of Stake
Status: ✅ Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kianenigma @bkchr @Ank4n