Backend engineer with a physics background (MSc Physics of Complex Systems). 5+ years in Rust/Go: multi-chain settlement (founded icRamp — ETHPrague 2024 winner + Internet Computer Foundation grant), low-latency execution, and production services with on-call and postmortems. I ran a public series of ZK/cryptography labs, maintain a Rust crate (dag_exec), and write about systems and security at reymom.xyz. Most interested in backend/distributed systems, security, and crypto/ZK infrastructure.
Yeah... the on-chain payload delivery is a clever evolution, it removes the static artifact entirely. In this case they used a similar approach but with a Vercel-hosted serverless endpoint as the loader instead of on-chain data. Same principle, nothing malicious exists in the repo itself, payload is fetched at runtime. The two-stage split (ephemeral loader vs persistent TCP C2) was the part I hadn't seen well-documented before.
Remote: Yes (remote-first; also open to on-site/hybrid in Barcelona)
Willing to relocate: Open
Technologies: Rust, Go, Python, TypeScript · distributed systems, gRPC/REST, PostgreSQL, Redis, Docker, Kubernetes, Linux · EVM/Solana/ICP, Solidity · applied cryptography & ZK (Ligero, LatticeFold, TEE/attestation labs)
Résumé/CV: https://reymom.xyz · https://github.com/reymom
Email: reymon.devs@gmail.com
Backend engineer with a physics background (MSc Physics of Complex Systems). 5+ years in Rust/Go: multi-chain settlement (founded icRamp — ETHPrague 2024 winner + Internet Computer Foundation grant), low-latency execution, and production services with on-call and postmortems. I ran a public series of ZK/cryptography labs, maintain a Rust crate (dag_exec), and write about systems and security at reymom.xyz. Most interested in backend/distributed systems, security, and crypto/ZK infrastructure.
reply