Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Consider further isolation of consensus related code #13449

@davxy

Description

@davxy

We already have primitive/consensus and client/consensus folders to keep together consensus related code.

Currently these folders contains code for protocols related to block authoring such as BABE, AURA, PoW and some shared utility code.

I propose to add to these folders everything related to consensus (thus also finality) such as grandpa and beefy crates.

Even though this is not paramount, I can't see any good reason to have these crates floating with the rest of the code.
In general I think is a good practice to logically organize the code.

If there isn't any drawback I can easily take on this trivial chore.

Metadata

Metadata

Assignees

Labels

I7-refactorCode needs refactoring.Z0-trivialWriting the issue is of the same difficulty as patching the code.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions