A language built for the exact problems blockchains have
Blockchain infrastructure has two requirements that are unusually hard to satisfy at the same time: it has to run fast, because validators and nodes are racing against real-world clocks and each other, and it has to be extremely safe, because a single bug in code that moves value can be catastrophic and irreversible in a way a bug in a photo-editing app never is. Most languages force a tradeoff between those two goals. Garbage-collected languages like Go or Java make memory management safer and easier, but the garbage collector introduces unpredictable pauses, which is a real problem for software that needs consistent, low-latency performance. Languages like C and C++ give you full control and speed with no garbage collector, but that control comes at the cost of manual memory management, which is a well-documented source of serious bugs.
Rust was designed specifically to close that gap. It compiles to fast, low-level machine code with no garbage collector and no runtime overhead for memory safety, because the safety guarantees are enforced by the compiler before the program ever runs, not by a background process while it's running. That combination, C-like performance with compile-time memory safety, is precisely what performance-critical, security-critical blockchain infrastructure needs, which is why it shows up so consistently across the space: Solana's validator client and on-chain programs are written in Rust, a substantial and growing share of newer Bitcoin tooling is written in Rust, and a number of newer Layer 1 blockchains chose Rust as their primary implementation language from the start.