What is your name?
Daniel Dia
What is your preferred email address?
danieldia25519@gmail.com
Do you represent a company, institution, consortium, yourself or other entity?
Myself.
If you represent a company, institution, consortium, or other entity, please enter it here.
Individual.
Why are you interested in joining the Safety Critical Rust Consortium?
I'm a second-year Computer & Communications Engineering (CCE) and Math student at the American University of Beirut (AUB), and I've been spending a lot of my time thinking about how to make software provably, structurally correct.
The work I'm most actively invested in right now is hpke-ng, a clean-slate Rust implementation of RFC 9180 that I've been co-developing with Dr. Nadim Kobeissi. The library takes a strong position on type-driven design, ensuring that mismatched primitives, wrong-mode calls, and nonce reuse are compile errors, not runtime surprises. My contributions included benchmarks (132 head-to-head comparisons against the two major competing Rust HPKE libraries), documentation, and tests covering roundtrips across every ciphersuite × mode combination, as well as compile-fail invariants. I'm currently working on further performance and code quality improvements. Working on a cryptographic primitive where correctness isn't optional has made the stakes of safety-critical software (particularly in Rust) feel very concrete.
The Consortium feels like the right community to be part of: people doing the hard work of making Rust usable where getting it wrong isn't an acceptable outcome. I'd like to contribute to that, and honestly, to learn from people who are further along in figuring it out than I am.
Do you plan to be a producer or observer in the consortium?
Producer
What is your name?
Daniel Dia
What is your preferred email address?
danieldia25519@gmail.com
Do you represent a company, institution, consortium, yourself or other entity?
Myself.
If you represent a company, institution, consortium, or other entity, please enter it here.
Individual.
Why are you interested in joining the Safety Critical Rust Consortium?
I'm a second-year Computer & Communications Engineering (CCE) and Math student at the American University of Beirut (AUB), and I've been spending a lot of my time thinking about how to make software provably, structurally correct.
The work I'm most actively invested in right now is
hpke-ng, a clean-slate Rust implementation of RFC 9180 that I've been co-developing with Dr. Nadim Kobeissi. The library takes a strong position on type-driven design, ensuring that mismatched primitives, wrong-mode calls, and nonce reuse are compile errors, not runtime surprises. My contributions included benchmarks (132 head-to-head comparisons against the two major competing Rust HPKE libraries), documentation, and tests covering roundtrips across every ciphersuite × mode combination, as well as compile-fail invariants. I'm currently working on further performance and code quality improvements. Working on a cryptographic primitive where correctness isn't optional has made the stakes of safety-critical software (particularly in Rust) feel very concrete.The Consortium feels like the right community to be part of: people doing the hard work of making Rust usable where getting it wrong isn't an acceptable outcome. I'd like to contribute to that, and honestly, to learn from people who are further along in figuring it out than I am.
Do you plan to be a producer or observer in the consortium?
Producer