sbpf-linker 0.2.3: Blueshift Says Solana Programs Now Build on Upstream Rust and LLVM

Blueshift's sbpf-linker 0.2.3 reached crates.io at 08:03 UTC on 9 October 2026 and was tagged on GitHub the same day. Claire Fan, the Blueshift developer who wrote the release's main changes, says the version lets developers compile a Solana SOL$109.70+1.0% program with the ordinary Rust nightly compiler, with no Solana-specific fork of Rust or LLVM involved.

How sbpf-linker builds Solana programs from upstream Rust and LLVM

Solana programs run as sBPF, a bytecode format derived from eBPF. Producing that bytecode has meant using a modified compiler. Anza's platform-tools repository says it builds "Clang and Rust compiler binaries that incorporate customizations and fixes required by Solana but not yet upstreamed into Rust or LLVM", drawing on Anza-maintained forks of Rust, LLVM, Cargo, compiler-builtins and newlib.

sbpf-linker takes a different route. The project README describes the tool as "an upstream BPF linker to relink upstream BPF binaries into an SBPF V0/V3 compatible binary format". The unmodified compiler targets generic BPF, and the linker, the tool that assembles compiled code into a finished program file, repackages the result into a file the Solana runtime accepts. Fan set out that two-step design in her Breakpoint 2025 talk on sBPF and compilers, where she argued that a forked compiler leaves Solana developers waiting for improvements made in mainline Rust and LLVM.

What changed in sbpf-linker 0.2.3: compiler builtins, stricter errors

The release notes list 13 changes from five contributors. Fan wrote three of them: a warning when the solana-compiler-builtins crate is missing, a default of sBPF v3 with the architecture flag hidden, and math builtins that are included by default. None of the three pull requests carries a description, so the repository does not document the reasoning behind them.

Builtins are small helper routines a compiler assumes are available for operations the target machine cannot do directly. solana-compiler-builtins, a separate Blueshift crate, provides "software implementations of intrinsics not natively supported by the SVM", the Solana Virtual Machine. Its list covers memory copy and compare, 128-bit integer multiplication and 64-bit floating-point arithmetic.

Two other changes make build failures harder to miss. The linker now reports every missing exported symbol at once, and a stack-argument overlap that used to produce a warning now stops the build.

Claire Fan's cargo +nightly build claim and what the README documents

Fan announced the release on X with the line: "For the first time in Solana history, we can generate Solana programs directly from upstream rustc and LLVM!" She added that "starting with sbpf-linker 0.2.3, you can compile a no_std Solana program with just cargo +nightly build". A no_std program is one that does not use Rust's standard library.

The approach itself is a year old: the first sbpf-linker crate was published on 11 October 2025, per crates.io. Fan's claim for 0.2.3 is that the flow now works with a plain Cargo command. The README has not caught up with that description. It documents cargo +nightly build-bpf through a project template, does not mention no_std, and has no section on known limitations. Fan's post says "anything that doesn't work should be considered a bug, and I'll fix it!"

Anza engineer Alessandro Decina responded on X: "this is the way, remove all the ad hoc slop". That is one engineer's comment. Solana Compass found no Anza statement about changing platform-tools.

sBPF v3 is the linker's default, and mainnet activation is still pending

The linker now targets sBPF v3 unless told otherwise. Solana's sBPF v3 upgrade page lists mainnet activation as expected with Agave 4.4 in November 2026, with a devnet date "to be determined". Once the feature activates, the page says, "the network rejects any deployment, upgrade, or finalization of a program built for sBPFv0, v1, or v2", while programs already onchain keep running. Developers trying the upstream flow before then should check which sBPF version their target cluster accepts.

sbpf-linker is MIT-licensed. The README recommends cargo binstall sbpf-linker; installing from source with cargo install sbpf-linker needs a Rust nightly no older than nightly-2026-08-05.