Today, enjoy the Lightspeed newsletter on Blockworks.co. Tomorrow, get the news delivered directly to your inbox. Subscribe to the Lightspeed newsletter.
At long last, the much-hyped Solana Firedancer client appears to be boogieing its way into the light.
Jump Trading chief scientist Kevin Bowers announced it in about the nerdiest way possible at Solana Breakpoint, pointing out to a crowd of onlookers that a string of numbers indicating a software version on Solana mainnet looked suspiciously unlike Solana’s current clients. This led to some applause.
Firedancer is an independent validator client, or software that validators can run to build the blockchain, being developed by Jump. The client is being written independently of the original Solana Labs validator client, now called Agave (in the programming language C) as opposed to Agave, written in Rust.
There are two versions of the client out there right now: Frankendancer, which is a slightly more performant version of the Agave client, and Firedancer, which is the whole hog. Frankendancer is coming out first and is built through replacing the Agave client piece by piece, like Frankenstein’s monster.
The high-level updates to the Firedancer project are that Frankendancer is live on mainnet, and Firedancer is live on testnet. Someone related to the project told me that another Firedancer update is coming tomorrow, but they wouldn’t say anything further.
Solana co-founder Anatoly Yakovenko has said that once Firedancer goes to mainnet, he would favor removing the “beta” qualifier from Solana’s “mainnet-beta” status.
Having multiple validator clients is important for a blockchain’s decentralization (Jito technically runs a separate validator client, but it’s very similar to the Agave client). With just one client, a bug in the code could threaten Solana’s live-ness. With multiple clients, the second client can step in and keep the blockchain running if the first is having issues. I’ve also heard it argued that with just one client, validators don’t have much of an option to opt out of Agave design choices unless they fork the blockchain, which would be a pretty extreme move. Helius CEO Mert Mumtaz and I spoke about this at greater length on the Lightspeed podcast here.
Besides decentralization, Firedancer is widely said to be much more performant than the Agave client. The client’s developers have spoken about hitting 1 million transactions per second (TPS) in a test environment. Solana usually handles around 3,000 TPS, and fewer if you only count non-vote transactions that involve users transacting, according to Solana Compass.
Solana Foundation executive director Dan Albert said there were “audible gasps” when a room of validators were shown Firedancer’s validator monitor GUI. If I was a betting man, I’d put a few bucks down that tomorrow’s update will have to do with Firedancer’s performance.
The client still has some time to go before reaching mainnet, and even then, users may not actually notice a difference in the blockchain, Lulo co-founder Jesse Brauner told me in a text.
Transactions “always happen fast and [users] won’t notice a millisecond level improvement,” Brauner wrote.
But either way, Firedancer is moving from idea to reality, and that’s always fun to see.
Start your day with top crypto insights from David Canellis and Katherine Ross. Subscribe to the Empire newsletter.
Explore the growing intersection between crypto, macroeconomics, policy and finance with Ben Strack, Casey Wagner and Felix Jauvin. Subscribe to the On the Margin newsletter.
The Lightspeed newsletter is all things Solana, in your inbox, every day. Subscribe to daily Solana news from Jack Kubinec and Jeff Albus.
- Lightspeed Newsletter
- Solana
- Validator