Skip to content

feature: Add beacon client to localnet testing #785

Description

@ClaytonNorthey92

Confirmation

  • I have checked for similar issues.

Problem

At the moment, we run localnet in --dev mode for our L1. Consequently, we don't require a beacon client. However, in doing this, we miss out on some crucial testing paths.

Suggested solution

Add a beacon client to localnet's L1. Ensure that this beacon client as all forks active.

Additional Information

We may need to change localnet from PoA to PoS.

Metadata

Metadata

Labels

status: in progressThis issue is currently being worked on. This label helps avoid duplicating workstatus: triageThis is awaiting review. Maintainers should this label once triagedtype: enhancementThis improves existing functionalitytype: testThis adds or improves test coverage

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions