Thomas Eizinger
Software Engineer
Sydney, New South Wales, Australia
Summary
🤩
RockstarThomas Eizinger is a software engineer based in Sydney with 11 years of hands-on experience building secure, back-end systems and contributing to major open-source projects. He’s a Rust enthusiast who has made substantive contributions to libp2p, rust-secp256k1, and testcontainers-rs, and co-created nobt-io while helping secure traffic at Firezone, a WireGuard-based zero-trust platform. His work blends low-level crypto and networking expertise—implementing HTLC examples for miniscript and refining stream management in libp2p—with pragmatic refactors that improve maintainability and developer ergonomics. Colleagues describe him as a disciplined developer focused on better habits and practical security improvements rather than flashy surface-level features.
11 years of coding experience
Github Skills (39)
algorithm10
unit-testing10
min10
algorithms10
docker10
lib10
back-end-development10
api-design10
elixir10
peer-to-peer10
code-library10
dockers10
networking10
wireguard10
script10
Programming languages (29)
Github contributions (5)
libp2p/rust-libp2p
Apr 2020 - Jan 2023
The Rust Implementation of the libp2p networking stack.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:2 releases, 3803 reviews, 922 commits in 2 years 10 months
Contributions summary:Thomas primarily contributed to the core logic of the libp2p networking stack, addressing specific edge cases and extending feature flags. The user made changes related to managing streams and various network operations. They addressed build issues and implemented new features.
rustp2pnetworkingpeer-to-peernetwork
testcontainers/testcontainers-rs
Aug 2018 - Oct 2022
A library for integration-testing against docker containers from within Rust.
Role in this project:Back-end Developer
Back-end DeveloperContributions:2 releases, 230 reviews, 221 commits in 4 years 3 months
Contributions summary:Thomas primarily worked on refactoring the codebase by removing the concept of `ContainerClient` and replacing it with a closure-based approach. They included an example for `bitcoin_rpc`, fixed build issues, and adapted code to breaking API changes within the `hmac` crate. Further contributions included restructuring the crate for better usability by splitting it into core and cli_client crates. They also worked on fixing examples after refactoring and upgrading the `coblox_bitcoincore` dependency.
containersrusttestingdockerdocker-containers
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.