HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
firedancer-io
firedancer
C2024–2026
firedancer-io / firedancer

firedancer

Firedancer is Jump Crypto's Solana validator software.

3Distinct people
13Mentions
0Explicit recommenders
1.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Firedancer is Jump Crypto's Solana validator software.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month13 dated mentions

Observed mentions: 2024-09-13 04:36:19 UTC to 2026-02-02 18:58:45 UTC.

01232024-09-01 00:00:00 UTC to 2024-10-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsSep 20242024-10-01 00:00:00 UTC to 2024-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-11-01 00:00:00 UTC to 2024-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2025-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-01 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 20252025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 20242024-09-01 00:00:00 UTC2024-10-01 00:00:00 UTC303
Oct 20242024-10-01 00:00:00 UTC2024-11-01 00:00:00 UTC000
Nov 20242024-11-01 00:00:00 UTC2024-12-01 00:00:00 UTC000
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC000
Feb 20252025-02-01 00:00:00 UTC2025-03-01 00:00:00 UTC101
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC000
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC000
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC101
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC101
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC101
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC101
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC101
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC101
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC101
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC101

What Hacker News says

13 sources
Unto Labs | San Francisco, CA | ONSITE (Hybrid OK), REMOTE (US) | Full-Time Unto Labs is developing the Thru Layer-1 blockchain (https://thru.org) We recently announced $14.4 million in funding to make blockchains & digital assets useful for the world. Founded by Jump Crypto alumni and core contributors to the Solana protocol and the Firedancer client (https://github.com/firedancer-io/firedancer), we’re tackling fundamental scalability, performance, and usability challenges in distributed ledgers. Our runtime conforms to the RISC-V specification—moving away from domain-specific VMs, DSLs, and bespoke compiler toolchains that limit developer and institutional adoption. You can write smart contracts and programs in any LLVM compatible programming language and reason about a standard ISA in RISC-V. Components are developed in C for maximal c
Read the rest
ontrol over performance and resource usage. We believe there is a unique window of opportunity to developer fairer, more accessible, and more global financial products on resilient public blockchains. You can check out our docs and open-source developer tooling at docs.thru.org and https://github.com/Unto-Labs/thru/ We are hiring for the following role(s): - Systems Engineer: https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5...
In Ask HN: Who is hiring? (February 2026)
Unto Labs | San Francisco, CA | ONSITE (Hybrid OK), REMOTE (US) | Full-Time Unto Labs is developing the Thru Layer-1 blockchain (https://thru.org) We recently announced $14.4 million in funding to make blockchains & digital assets useful for the world. Founded by Jump Crypto alumni and core contributors to the Solana protocol and the Firedancer client (https://github.com/firedancer-io/firedancer), we’re tackling fundamental scalability, performance, and usability challenges in distributed ledgers. Our runtime conforms to the RISC-V specification—moving away from domain-specific VMs, DSLs, and bespoke compiler toolchains that limit developer and institutional adoption. You can write smart contracts and programs in any LLVM compatible programming language and reason about a standard ISA in RISC-V. Components are developed in C for maximal c
Read the rest
ontrol over performance and resource usage. We believe there is a unique window of opportunity to developer fairer, more accessible, and more global financial products on resilient public blockchains. You can check out our docs and open-source developer tooling at docs.thru.org and https://github.com/Unto-Labs/thru/ We are hiring for the following role(s): - Systems Engineer: https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5...
In Ask HN: Who is hiring? (December 2025)
Unto Labs | San Francisco, CA | ONSITE (Hybrid OK), REMOTE (US) | Full-Time Unto Labs is developing the Thru Layer-1 blockchain (https://thru.org) We recently announced $14.4 million in funding to make blockchains & digital assets useful for the world. Founded by Jump Crypto alumni and core contributors to the Solana protocol and the Firedancer client (https://github.com/firedancer-io/firedancer), we’re tackling fundamental scalability, performance, and usability challenges in distributed ledgers. Our runtime conforms to the RISC-V specification—moving away from domain-specific VMs, DSLs, and bespoke compiler toolchains that limit developer and institutional adoption. You can write smart contracts and programs in any LLVM compatible programming language and reason about a standard ISA in RISC-V. Components are developed in C for maximal c
Read the rest
ontrol over performance and resource usage. We believe there is a unique window of opportunity to developer fairer, more accessible, and more global financial products on resilient public blockchains. You can check out our docs and open-source developer tooling at docs.thru.org and https://github.com/Unto-Labs/thru/ We are hiring for the following role(s): - Systems Engineer: https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5...
In Ask HN: Who is hiring? (November 2025)
Unto Labs | San Francisco, CA | ONSITE (Hybrid OK), REMOTE (US) | Full-Time Unto Labs is developing the Thru Layer-1 blockchain (https://thru.org) We recently announced $14.4 million in funding to make blockchains & digital assets useful for the world. Founded by Jump Crypto alumni and core contributors to the Solana protocol and the Firedancer client (https://github.com/firedancer-io/firedancer), we’re tackling fundamental scalability, performance, and usability challenges in distributed ledgers. Our runtime conforms to the RISC-V specification—moving away from domain-specific VMs, DSLs, and bespoke compiler toolchains that limit developer and institutional adoption. You can write smart contracts and programs in any LLVM compatible programming language and reason about a standard ISA in RISC-V. Components are developed in C for maximal c
Read the rest
ontrol over performance and resource usage. We believe there is a unique window of opportunity to developer fairer, more accessible, and more global financial products on resilient public blockchains. We are hiring for the following roles: - Systems Engineer: https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5... - Software Engineer, Developer Tools: https://jobs.ashbyhq.com/unto-labs/1ae2769b-1a67-41e2-a8d6-5...
In Ask HN: Who is hiring? (October 2025)
Unto Labs | San Francisco, CA | ONSITE (Hybrid OK), REMOTE (US) | Full-Time Unto Labs is developing the Thru Layer-1 blockchain (https://thru.org) We recently announced $14.4 million in funding to make blockchains & digital assets useful for the world. Founded by Jump Crypto alumni and core contributors to the Solana protocol and the Firedancer client (https://github.com/firedancer-io/firedancer), we’re tackling fundamental scalability, performance, and usability challenges in distributed ledgers. Our runtime conforms to the RISC-V specification—moving away from domain-specific VMs, DSLs, and bespoke compiler toolchains that limit developer and institutional adoption. You can write smart contracts and programs in any LLVM compatible programming language and reason about a standard ISA in RISC-V. Components are developed in C for maximal c
Read the rest
ontrol over performance and resource usage. We believe there is a unique window of opportunity to developer fairer, more accessible, and more global financial products on resilient public blockchains. We are hiring for the following roles: - Systems Engineer: https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5... - Design Engineer: https://jobs.ashbyhq.com/unto-labs/81cbbb75-a75a-4d96-b5da-7... - Product Engineer: https://jobs.ashbyhq.com/unto-labs/1ae2769b-1a67-41e2-a8d6-5...
In Ask HN: Who is hiring? (September 2025)
Unto Labs | San Francisco, CA | ONSITE (Hybrid OK), REMOTE (US) | Full-Time Unto Labs is developing the Thru Layer-1 blockchain (https://thru.org) We recently announced $14.4 million in funding to make blockchains & digital assets useful for the world. Founded by Jump Crypto alumni and core contributors to the Solana protocol and the Firedancer client (https://github.com/firedancer-io/firedancer), we’re tackling fundamental scalability, performance, and usability challenges in distributed ledgers. Our runtime conforms to the RISC-V specification—moving away from domain-specific VMs, DSLs, and bespoke compiler toolchains that limit developer and institutional adoption. You can write smart contracts and programs in any LLVM compatible programming language and reason about a standard ISA in RISC-V. Components are developed in C for maximal c
Read the rest
ontrol over performance and resource usage. We believe there is a unique window of opportunity to developer fairer, more accessible, and more global financial products on resilient public blockchains. We are hiring for the following roles: - Systems Engineer: https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5... - Design Engineer: https://jobs.ashbyhq.com/unto-labs/81cbbb75-a75a-4d96-b5da-7... - Product Engineer: https://jobs.ashbyhq.com/unto-labs/1ae2769b-1a67-41e2-a8d6-5...
In Ask HN: Who is hiring? (August 2025)
Unto Labs | Systems Engineer | San Francisco, CA | ONSITE (Hybrid OK), REMOTE (US) | Full-Time | https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5... We recently announced $14.4 million in funding to make blockchains & digital assets useful for the world. Founded by Jump Crypto alumni and core contributors to the Solana protocol and the Firedancer client (https://github.com/firedancer-io/firedancer), we’re tackling fundamental scalability, performance, and usability challenges in distributed ledgers. Our runtime conforms to the RISC-V specification—moving away from domain-specific VMs, DSLs, and bespoke compiler toolchains that limit developer and institutional adoption. Components are developed in C for maximal control over performance and resource usage. Interesting problems you’ll tackle: - Building and testing high-performa
Read the rest
nce subsystems in C (cryptographic routines, consensus primitives, networking protocols) - Designing robust process isolation on modern CPU architectures and tile-based multi-core layouts - Optimizing memory hierarchies, cache utilization, and low-level I/O for commodity servers You: - 5+ years of systems programming in C/C++, Rust, or similar - Deep expertise in CPU microarchitecture, memory subsystems, and low-level performance tuning - Strong understanding of distributed systems design and consensus protocols - Experience with high-performance networking and protocol design in real-time environments Apply: https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5...
In Ask HN: Who is hiring? (July 2025)
Unto Labs | Systems Engineer | San Francisco, CA | ONSITE (Hybrid OK), REMOTE (US) | Full-Time | https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5... We recently announced $14.4 million in funding to make blockchains & digital assets useful for the world. Founded by Jump Crypto alumni and core contributors to the Solana protocol and the Firedancer client (https://github.com/firedancer-io/firedancer), we’re tackling fundamental scalability, performance, and usability challenges in distributed ledgers. Our runtime conforms to the RISC-V specification—moving away from domain-specific VMs, DSLs, and bespoke compiler toolchains that limit developer and institutional adoption. Components are developed in C for maximal control over performance and resource usage. Interesting problems you’ll tackle: - Building and testing high-performa
Read the rest
nce subsystems in C (cryptographic routines, consensus primitives, networking protocols) - Designing robust process isolation on modern CPU architectures and tile-based multi-core layouts - Optimizing memory hierarchies, cache utilization, and low-level I/O for commodity servers You: - 5+ years of systems programming in C/C++, Rust, or similar - Deep expertise in CPU microarchitecture, memory subsystems, and low-level performance tuning - Strong understanding of distributed systems design and consensus protocols - Experience with high-performance networking and protocol design in real-time environments Apply: https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5...
In Ask HN: Who is hiring? (June 2025)
Unto Labs | Systems Engineer | San Francisco, CA | ONSITE (Hybrid OK), REMOTE (US) | Full-Time | https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5... We recently announced $14.4 million in funding to make blockchains & digital assets useful for the world. Founded by Jump Crypto alumni and core contributors to the Solana protocol and the Firedancer client (https://github.com/firedancer-io/firedancer), we’re tackling fundamental scalability, performance, and usability challenges in distributed ledgers. Our runtime conforms to the RISC-V specification—moving away from domain-specific VMs and bespoke compiler toolchains that limit developer and institutional adoption. Components are developed in C for maximal control over performance and resource usage. Interesting problems you’ll tackle: - Building and testing high-performance sub
Read the rest
systems in C (cryptographic routines, consensus primitives, networking protocols) - Designing robust process isolation on modern CPU architectures and tile-based multi-core layouts - Optimizing memory hierarchies, cache utilization, and low-level I/O for commodity servers You: - 5+ years of systems programming in C/C++, Rust, or similar - Deep expertise in CPU microarchitecture, memory subsystems, and low-level performance tuning - Strong understanding of distributed systems design and consensus protocols - Experience with high-performance networking and protocol design in real-time environments Apply: https://jobs.ashbyhq.com/unto-labs/13df6bea-b253-4c80-ae05-5...
In Ask HN: Who is hiring? (May 2025)
As an example, the Amazon implementation doesn't refer to gcc's[1] and clang's[2] "zero_call_used_regs" to zeroise CPU registers upon return or exception of functions working on crypto secrets. OpenSSL doesn't either.[3] firedancer _does_ use "zero_call_used_regs" to allow gcc/clang to zeroise used CPU registers.[9] As another example, the Amazon implementation also doesn't refer to gcc's "strub" attribute which zeroises the function's stack upon return or exception of functions working on crypto secrets.[4][5] OpenSSL doesn't either.[3] firedancer _does_ use the "strub" attribute to allow gcc to zeroise the function's stack.[9] Is there a performance impact? [6] has the overhead at 0% for X25519 for implementing CPU register and stack zeroisation. Compiling the Linux kernel with "CONFIG_ZERO_CALL_USED_REGS=1" for x64_64 (impacting all ke
Read the rest
In Better-performing “25519” elliptic-curve cryptography
It's much more than just performance they've thought about. Here are some of the secure programming practices that have been implemented: /* All the functions in this file are considered "secure", specifically: - Constant time in the input, i.e. the input can be a secret[2] - Small and auditable code base, incl. simple types - Either, no local variables = no need to clear them before exit (most functions) - Or, only static allocation + clear local variable before exit (fd_ed25519_scalar_mul_base_const_time) - Clear registers via FD_FN_SENSITIVE[3] - C safety */ libsodium[4] implements similar mechanisms, and Linux kernel encryption code does too (example: use of kfree_sensitive)[5]. However, firedancer appears to better avoid moving secrets outside of CPU registers, and [3] explains that libraries such a
Read the rest
In Better-performing “25519” elliptic-curve cryptography

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.