Jump Crypto's Firedancer Client Launches on Solana Mainnet

iconKuCoinFlash
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
On-chain news emerged as Jump Crypto’s Firedancer client launched on Solana mainnet and began producing blocks. Founding engineer Ritchie Patel said the client has processed tens of millions of transactions in production. The team is rolling out the client gradually to avoid mass validator migration prior to complete security audits. Firedancer’s design is inspired by high-frequency trading systems. A public security audit contest with a $1 million bug bounty was recently held. Crypto news outlets such as Blockbeats reported the update.

BlockBeats report: On May 17, Firedancer, the Solana validator client developed by Jump Crypto, Jump Trading’s crypto division, went live on the Solana mainnet and began producing blocks. Firedancer’s founding engineer, Ritchie Patel, stated that the client has already processed tens of millions of transactions in production; however, the team will continue a gradual rollout and does not wish for validators to switch en masse until security audits are fully completed.


Additionally, Patel said that the Firedancer architecture draws heavily from traditional finance high-frequency trading systems, and the team recently completed a public security audit competition featuring a $1 million bug bounty pool. (CoinDesk)

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.