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.

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

Reenable BEEFY on Rialto #1286

Closed
svyatonik opened this issue Jan 17, 2022 · 2 comments
Closed

Reenable BEEFY on Rialto #1286

svyatonik opened this issue Jan 17, 2022 · 2 comments
Assignees
Labels
A-chores Something that has to be done, as part of regular maintenance

Comments

@svyatonik
Copy link
Contributor

BEEFY has been disabled in #1273 (I was thinking that enable_beefy is enough, but apparently it isn't). I'll disable alerts in #1285, so they also need to be reenabled after BEEFY is fixed

@svyatonik svyatonik added the A-chores Something that has to be done, as part of regular maintenance label Jan 17, 2022
@svyatonik svyatonik added this to the Kusama <> Polkadot Phase 2 milestone Jan 17, 2022
@acatangiu acatangiu self-assigned this Apr 14, 2022
@acatangiu
Copy link
Collaborator

I think we can change the polkadot service file to use a deny-list of chain-spec-names instead of using an allow-list as it is right now.
That way we can explicitly keep it disabled on Polkadot, Kusama, Westend, while any other chain reusing the polkadot service file can choose for themselves whether to enable BEEFY using the enable_beefy flag.

@svyatonik
Copy link
Contributor Author

closed in #1385

svyatonik pushed a commit that referenced this issue Jul 17, 2023
* Add event with XCM executor outcome, which includes weight fee

* Show weight used in processed messages

* remove added event

* named events

* message_id for message_hash

* Update pallets/xcmp-queue/src/lib.rs

Co-authored-by: joe petrowski <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-chores Something that has to be done, as part of regular maintenance
Projects
None yet
Development

No branches or pull requests

2 participants