SIMD-0196

Migrate Stake to Core BPF

Author: Hanako Mumei · Category: Core Protocol GitHub →

Feature Gate Status

Mainnet Active E823
Testnet Active E800
Devnet Active E917

6M4oQ6eXneVhtLoiAr4yRYQY43eVLjrKbiDZDJc892yk

TL;DR

Migrate the Stake program to Core BPF.

Summary

Migrate the Stake 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 Stake program should be migrated to Core BPF.

Impact

Validator client teams are no longer required to implement and maintain the Stake program within their runtime. All validator client teams can work to maintain the single Stake 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.