Rust Protocol Engineer — Autheo | Live Mainnet Consensus, P2P Networking & Node Performance

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 Protocol Engineer — Autheo Internet Operating System | Live Mainnet Consensus, P2P Networking & Node Performance Job code: LA385

About the Role

Autheo is recruiting a Rust protocol engineer to work on the node itself: consensus-adjacent paths, peer-to-peer networking, state sync, storage, and the performance of the validator set.

Mainnet launched on May 14, 2026, with a decentralized validator set. The coordination layer is Cosmos-based, and Rust is a first-class path in the Eigensphere Engine. We want someone who has worked inside a real node: Substrate/Polkadot, a Cosmos/CometBFT stack, reth or another Ethereum client, Solana/Agave, Sui/Aptos, Fuel, or a libp2p-based network. You will make the Rust parts of the Autheo node faster, safer to upgrade, and easier to reason about.

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

1. Consensus and state

• Read, harden and extend the Rust components on the block production, validation and finality paths. Write down every invariant you rely on.


• Work on state storage and sync: Merkle/state-DB layout, pruning, snapshots, warp or fast sync, and replay tooling for the live chain.


• Make upgrades deterministic. A node built from the same commit must produce the same state, with no exceptions.

2. Networking

• Own the Rust P2P paths: peer discovery, gossip, request/response protocols, backpressure, and handling of peers that are slow, malicious or partitioned.


• Instrument the network so you can explain a missed block or a slow sync from metrics and traces rather than guesswork.

3. Node performance

• Profile hot paths (block import, signature verification, state reads/writes, mempool) on replay and on Mainnet. Report p50/p99 latency, allocations and throughput you actually measured.


• Put benchmarks in CI (criterion or equivalent) so a performance regression fails the build.


• We don’t publish throughput numbers the cluster hasn’t measured.

4. Reliability with SRE

• Work with Site Reliability on validator and RPC operations: readiness and health signals, upgrade runbooks, and incident write-ups for any node-level fault.


• OpenTelemetry/Prometheus coverage on the paths you own.

Required

• Public Rust you wrote. A GitHub/GitLab profile, crates.io crate, or merged pull requests to a public Rust project, ideally node, networking or storage code. We read the code before we read the resume. Applications without a link to Rust code you wrote yourself will not be reviewed.


• Production Rust: ownership, lifetimes, async (Tokio or equivalent), and concurrency you’ve debugged under load.


• Hands-on work in at least one real blockchain or distributed-consensus codebase (Substrate, Cosmos SDK/CometBFT or a Rust ABCI stack, reth/Lighthouse, Agave/Solana, Sui/Aptos, Fuel, Narwhal/Bullshark/HotStuff-family, Raft/Paxos in production). Name the repository and your part in it.


• Networking depth: libp2p, QUIC, gossip protocols or an equivalent you can explain at the level of message types and failure modes.


• Comfortable with Linux performance tools (perf, flamegraphs, heaptrack or equivalent) and a CI pipeline that builds and tests Rust.

Preferred

• Contributions to rust-libp2p, smoldot, Substrate/polkadot-sdk, reth, Lighthouse, Agave, Sui, Aptos, Fuel, NOMT or a comparable project.


• Light clients, state sync, or storage engines (RocksDB, MDBX, Merkle-Patricia/JMT/NOMT).


• IBC or cross-chain message handling.


• A public artifact we can read: a design doc, talk, paper or post-mortem.

First 90 Days

• A written map of the Rust surface in the Autheo node: what’s live, what’s stubbed and what’s risky, with a stop / continue / start list agreed with protocol and SRE.


• One consensus, sync or networking path measured on replay, covered in CI and documented.


• A benchmark in CI for one hot function, with the number you’re willing to put next to your name.


• A short design note for one improvement (for example faster sync, a peer-scoring change, or a state-pruning plan) that has been reviewed by protocol leads.

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 node itself: consensus, P2P and state sync for a validator set that’s already live.


• 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.