Rust Cryptography Engineer — Autheo | Post-Quantum Signatures, ZK Verification & TheoID on Live Mainnet

Shape the Future of Blockchain—Bringing Business On-Chain

We’re offering a unique opportunity to join Launch Legends (and Autheo) as a part-time Equity Cofounder. Founded in July 2021, Launch Legends is at the forefront of bridging Web3 blockchain technology with the next evolution of Web2 integration—bringing businesses on-chain through enterprise-grade solutions, DePIN innovations, and decentralized financial infrastructure.

Our flagship project, Autheo, is an AI-enabled Layer-0 Operating System with an integrated Layer-1 blockchain and complete decentralized infrastructure that includes decentralized compute, storage, identity, and service marketplaces, as well as a full-stack development environment (DevHub)—engineered for scalable enterprise adoption, developer innovation, and real-world blockchain integration.

Our Projects

• Autheo — https://www.autheo.com


• THEO token launch & verified markets — https://www.autheo.com/token-launch


• Docs — https://docs.autheo.com


• Autheo Team — https://www.autheo.com/teams


• Launch Legends (Parent Company) — https://www.launchlegends.io


• X / Twitter — https://x.com/Autheo_Network

About Autheo

With nearly 100 equity cofounders from leading companies and institutions—many with advanced degrees and PhDs—Autheo is solving the critical challenges blocking business adoption of blockchain technology.

Autheo Mainnet launched on May 14, 2026 (Chain ID 2127), with staking and transaction fees on-chain. DevHub is available to builders. Sovereign identity (TheoID), decentralized compute and persistent storage through the Autheo Marketplace, AI inference (THEO AI), and post-quantum cryptography are rolling out on Mainnet.

THEO is live. This role starts after mainnet, not before it.

THEO trades on Autheo-verified markets, with Enflux supporting liquidity across the venues.

Verified trading links, contract addresses, and network information: https://www.autheo.com/token-launch

Key Features

• Layer-0 OS + Layer-1 — Sovereign Cosmos-based coordination layer with an EVM-compatible execution environment, IBC interoperability, and Proof of Autheo consensus.


• Eigensphere Engine — Multi-language runtime. Rust is a first-class path for execution, cryptography, and developer tooling, alongside Go, Solidity, Move, Vyper, and C.


• DevHub & full-stack SDKs — One workspace for frontend, backend, smart contracts, and orchestration.


• TheoID — Sovereign identity for people, services, and AI agents, with a post-quantum roadmap (Kyber, Dilithium, Falcon / NIST ML-KEM, ML-DSA, SLH-DSA).


• Autheo Marketplace — Decentralized compute, storage, and service markets rolling out on Mainnet.


• THEO AI — Inference and agent orchestration as a native primitive, not a third-party bolt-on.


• DePIN infrastructure — On-chain networks for real-world infrastructure ownership and resource sharing.

Traction

• Mainnet: Launched May 14, 2026, with on-chain staking, fees and a decentralized validator set.


• Public testnet history: a large, active builder and user community before Mainnet.


• Audits: Halborn (testnet and validator node platform), CertiK (Mainnet and smart contracts), Adevar Labs (Base to Autheo Mainnet bridge).


• THEO markets: verified venues on MEXC, Hydrex on Base, and Uniswap on Robinhood Chain, with Enflux as liquidity partner across DEX and CEX.


• Token: THEO, the native utility coin of the Autheo network.


• Organization: Launch Legends Inc., a Wyoming corporation, parent of Autheo LLC. Stewarded in part by the Autheo Foundation. 100+ equity cofounders across 25+ countries.

Compensation & Growth Path

This is a part-time equity / token-based cofounder opportunity. You will receive equity in Launch Legends, Autheo, and the WFO Creator Network, along with token allocations in the Autheo blockchain. THEO is already trading; this is an allocation in a live utility token, not a promise against a future TGE. We have already completed an initial financing round to support infrastructure and marketing, and are currently in discussions with VCs and crypto investors to fund expansion and salaries. There is no cash salary for this role today, and the commitment is at least 20 hours per week.

ROLE: Rust Cryptography Engineer — Autheo Internet Operating System | Post-Quantum Signatures, ZK Verification & TheoID Job code: LA386

About the Role

Autheo is recruiting an applied cryptography engineer who writes production Rust. The post-quantum roadmap (ML-KEM / Kyber, ML-DSA / Dilithium, Falcon, SLH-DSA) and zero-knowledge verification are moving onto Autheo Mainnet, launched May 14, 2026, starting with TheoID, Autheo’s sovereign identity for people, services and AI agents.

We want someone who has implemented cryptography against a spec and test vectors, not someone who has only called a library. Strong backgrounds include RustCrypto, dalek, arkworks, Plonky2/Plonky3, halo2, RISC Zero/SP1, Penumbra/Zcash, PQClean/liboqs bindings, or an audit firm’s Rust practice.

Part-time does not mean advisory. Equity cofounder means you own a surface, write the code, and review the code next to it.

1. Post-quantum primitives

• Integrate ML-KEM and ML-DSA (and evaluate Falcon / SLH-DSA) behind versioned Rust interfaces that the node, TheoID and the SDKs can call.


• Plan the migration: hybrid classical + PQ signatures, key and address formats, signature sizes and their effect on block and transaction size, and how to roll it out on a live chain.


• Constant-time code, zeroization, fuzzing and known-answer tests from NIST vectors. Every primitive gets a test against the spec.

2. Zero-knowledge verification

• Build or integrate proof-verification libraries that embed in the runtime. Name the proving system, and measure proof size and verify time.


• Work out where ZK actually helps Autheo (TheoID selective disclosure, Marketplace job attestation, bridge proofs) and write down where it doesn’t.

3. Keys, identity and threat models

• Key handling, rotation and recovery for TheoID, plus field-level encryption boundaries for Marketplace metadata.


• A written threat model for each surface you ship, reviewed with security. Work with external auditors (Halborn, CertiK, Adevar Labs have audited Autheo before).

4. Performance and CI

• Benchmarks in CI for sign, verify, encapsulate and prove/verify paths, so a regression fails the build.


• Run cross-architecture tests (x86_64, aarch64, wasm32) where the code ships to those targets.

Required

• Public Rust cryptography you wrote. A GitHub/GitLab profile, crates.io crate, merged pull requests to a cryptography library, or a published paper with a Rust implementation. Applications without a link to Rust code you wrote yourself will not be reviewed.


• Production Rust: ownership, lifetimes, traits/generics over field or curve types, no_std awareness, and safe handling of secret material.


• You’ve implemented at least one cryptographic scheme from a spec or paper and validated it against test vectors. Tell us which one.


• Working knowledge of at least one of: lattice-based PQC (ML-KEM / ML-DSA / Falcon), hash-based signatures, SNARK/STARK proving systems, or elliptic-curve signatures and aggregation (Ed25519, BLS, Schnorr/FROST).


• Ability to explain side channels, nonce misuse, and malleability risks in code you’ve shipped.

Preferred

• Contributions to RustCrypto, dalek-cryptography, arkworks, Plonky2/3, halo2, RISC Zero, SP1, zkcrypto, Penumbra, Zcash or a comparable project.


• Audit experience on either side: you’ve written findings, or you’ve fixed them.


• Formal methods, fuzzing (cargo-fuzz, libFuzzer) or differential testing against a reference implementation.


• A PhD or published research in cryptography helps. It doesn’t replace code.

First 90 Days

• A written review of the cryptography that is live versus planned in Autheo, with a recommended PQ migration path (hybrid scheme, formats, rollout) agreed with protocol and security.


• One PQ signature or KEM path integrated behind a versioned interface, tested against NIST KATs, fuzzed, and benchmarked in CI.


• A design note on one ZK verification use case, with a named proving system and measured costs.

About Our Organization

Autheo is building a Layer-0 Operating System and an integrated Layer-1 so identity, compute, storage, developer tooling, and AI sit on one network instead of a pile of bridges. Mainnet is live. THEO is trading. The remaining work is product and protocol on that chain, not a promise of a future launch.

🌐 🚀 WHY JOIN LAUNCH LEGENDS?

• The chain is up. Staking, fees, DevHub, and verified THEO markets are already public.


• The Rust seat is on the cryptography path: post-quantum signatures, ZK verification and TheoID.


• Equity in Launch Legends and Autheo, plus a THEO allocation in a token that already trades.


• 100+ equity cofounders across 25+ countries. Remote. Direct line to the engineering leads and the Managing Directors.