Coin Brief ENDE

Firedancer merges runtime support for SIMD-0683 while the proposal is still in review

Firedancer merged pull request 12893 on 18 November, which implements SIMD-0683 in its runtime. The proposal, written by febo of Anza and still in Review status, gives programs three more values at the entrypoint of the ABIv1 virtual machine. Registers r1 and r2 already hold the input region pointer and the pointer to the instruction data; under SIMD-0683, r3 holds the instruction data length, r4 a pointer to the accounts slice and r5 the number of accounts, including duplicates.

The motivation in the proposal is to save work in every program. Once SIMD-0449 is active, a slice of account pointers is serialized into the program input, but programs still have to calculate where it starts relative to the instruction data. With the new registers, they can reconstruct both the instruction data and the accounts slice without calculating offsets or loading lengths. The registers are filled for all ABIv1 programs under all loaders, whether or not a program reads them; the deprecated ABIv0 loader is not supported.

The proposal lists the virtual machine as the only affected validator component. It considered changing the serialization layout instead but rejected that as a breaking change, and notes that ABIv2 will change the layout anyway, so the register approach gives an immediate benefit without conflicting with it.

Firedancer merges runtime support for SIMD-0683 while the proposal is still in review
Firedancer merges runtime support for SIMD-0683 while the proposal is still in review — Coin Brief

Why it matters

Each Solana program pays for parsing its input on every call, so a few registers filled once by the runtime save work across the whole chain. A second client implementing it is the step that makes activation possible once the proposal is accepted.

Primary source
GitHub - firedancer-io/firedancer
https://github.com/firedancer-io/firedancer/pull/12893
Written by Victoria Shinder.