SIMD-0140

Migrate Config to Core BPF

Author: Joe Caulfield - Anza Technology · Category: Core Protocol GitHub →

Feature Gate Status

Mainnet Active E753
Testnet Active E733
Devnet Active E817

2Fr57nzzkLYXW695UdDxDeR5fhnZWSttZeZYemrnpGFV

TL;DR

Migrate the Config program to Core BPF.

Summary

Migrate the Config program to Core BPF.

Motivation

BPF programs offer less complexity than native programs for other clients, such as Firedancer, since developers will no longer have to keep up with program changes in their runtime implementations. Instead, the program can just be updated once. In this spirit, the Config program should be migrated to Core BPF.

Impact

Validator client teams are no longer required to implement and maintain the Config program within their runtime. All validator client teams can work to maintain the single Config program together.

Backwards Compatibility

The Core BPF implementation is 100% backwards compatible with the original builtin implementation.

Security Considerations

The program's reimplementation poses no new security considerations compared to the original builtin version. The greatest security concern is a mistake in the reimplementation.