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

Unify Import verifier usage across parachain template and omninode. #7055

Open
skunert opened this issue Jan 6, 2025 · 0 comments
Open

Unify Import verifier usage across parachain template and omninode. #7055

skunert opened this issue Jan 6, 2025 · 0 comments
Labels
T0-node This PR/Issue is related to the topic “node”.

Comments

@skunert
Copy link
Contributor

skunert commented Jan 6, 2025

In omni node we use the standard aura verifier and add it to a compatibility layer to allow old blocks with relay-chain consensus to be imported:

let aura_verifier = cumulus_client_consensus_aura::build_verifier::<

In the parachain template we use a verifier that does some extra equivocation checks:

cumulus_client_consensus_aura::equivocation_import_queue::fully_verifying_import_queue::<

It checks that no more than EQUIVOCATION_LIMIT blocks are imported at the same slot.

Having the equivocation check is desirable, we should also use this one in the omni-node.

@skunert skunert added the T0-node This PR/Issue is related to the topic “node”. label Jan 6, 2025
@github-project-automation github-project-automation bot moved this to backlog in SDK Node Jan 6, 2025
@skunert skunert moved this to Milestone 1 in Polkadot Omni Node Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T0-node This PR/Issue is related to the topic “node”.
Projects
Status: Milestone 1
Status: backlog
Development

No branches or pull requests

1 participant