Senior Engineer, API & Interoperability — Autheo | Live Mainnet, IBC & Bridge APIs

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 —
• THEO token launch & verified markets —
• Docs —
• Autheo Team —
• Launch Legends (Parent Company) —
• X / Twitter —

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 has been live since May 14, 2026 (Chain ID 2127). Staking and transaction fees are operating 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 is Autheo’s native utility token, not a governance token. Autheo is not a DAO.

As of October 2, 2026 , THEO trades on four Autheo-verified markets across two chains and one centralized exchange, with Enflux supporting liquidity across the venues:

• THEO/USDT on MEXC — first centralized order book, opened October 1, 2026 at 13:00 UTC . Deposits are accepted on Autheo Mainnet (native THEO). Withdrawals opened October 2, 2026 at 13:00 UTC .
• THEO/USDC on Hydrex (Base) — live since August 20, 2026 . Official Base contract: 0xebE516a20238F79dc20b07eaD6768e08891Ed309
• THEO/USDG on Uniswap v3 (Robinhood Chain) — live since September 10, 2026
• THEO/NVDA on Uniswap (Robinhood Chain) — live since September 24, 2026 . Official Robinhood Chain contract: 0x3dc751e0da01812e6d9143cc696e7f07ea94da48

Verified trading links, contract addresses, and network information:

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.
• 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: Live since May 14, 2026 . Staking and fees on-chain. Secured by the live validator set (149 active of 156 total as of September 23, 2026).
• Public testnet history: 2 million+ wallets , 10 million+ transactions , 1.1 million+ smart contracts .
• Audits: Halborn (testnet and validator node platform), CertiK (Mainnet and smart contracts), Adevar Labs (Base to Autheo Mainnet bridge).
• THEO markets: Four verified venues — MEXC , Hydrex on Base , and two Uniswap pools on Robinhood Chain — with Enflux as liquidity partner across DEX and CEX.
• Token: THEO , native utility coin. Maximum supply 7.0 billion . Approximately 5.33% designated as initial circulating supply at the August 20, 2026 TGE ($0.05 reference price on Hydrex).
• 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. Salaried compensation is expected to begin within 4 to 5 months , following our node, token sales, or funding.

ROLE: Senior Engineer, API & Interoperability — Autheo | Live Mainnet, IBC & Bridge APIs Job code: LA381

About the Role

Autheo is recruiting a Senior Engineer, API & Interoperability to own the contracts other systems use to reach a chain that is already live.

Mainnet has been up since May 14, 2026 . It is EVM-compatible and IBC-connected . Staking and fees settle on-chain. THEO moves on Autheo Mainnet, and it already trades on Base and Robinhood Chain . Adevar Labs reviewed the Base to Autheo Mainnet bridge. DevHub is open. The job is the API and message path under that: gRPC, GraphQL, and REST for DevHub and partners; IBC packets and relaying; the bridge surface that already exists; event delivery a dApp can retry.

You write Go and Rust . You sit with Protocol and with SRE. SRE owns the hosts, the RPC tier, and the page. You own the schema, the packet, and the failure mode when a message tears. You do not own exchange listings, consensus design, or the grant file.

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

Key Responsibilities

1. API contracts

• Versioned gRPC and GraphQL for the paths DevHub and partners call: staking, fees, identity, and the Marketplace methods as they land. REST where a caller will not take a stub.
• Schema evolution, idempotency keys, and backpressure. A breaking change has a version, not a surprise.
• Go and Rust clients, plus a JavaScript binding DevHub can ship. Python if a partner is already on it.

2. IBC and the live bridge

• IBC channels and relaying against Autheo Mainnet. Packet timeout, ack, and the case where the other chain halts.
• The Base to Autheo bridge, and the Robinhood Chain path THEO already uses. Name the custody, the signer set, and what Adevar already reviewed before you add a route.
• Saga or an equivalent durable workflow where a multi-step flow can tear. Name the compensation step.

3. Events

• Logs and transactions out to dApps and DevHub: webhook or stream, idempotency, per-endpoint health, and a latency budget you can show on a trace.
• Exactly-once only if you can show the dedupe. At-least-once with a key is an acceptable design. A slogan is not.

4. Reliability of the path you own

• Kubernetes deploys, circuit breakers, and retries that match how SRE runs the platform.
• OpenTelemetry from the API call to the packet. A partner ticket should not require a private log.
• Benchmarks in CI on the hot adapter. Report what you measured.

5. Developer surface

• Docs and a sandbox so a caller can finish one cross-chain operation without reading the node.
• Reviews, a short design note, and mentorship of the engineers on the same surface.

Qualifications

Required

• 5+ years in protocol or API engineering.
• Production Go or Rust , and a second of gRPC, GraphQL, or both. Both languages if you have them.
• A bridge, an IBC path, XCM , CCIP , or an equivalent message layer you have operated. Name the chain and the failure.
• Distributed systems you can defend: retries, idempotency, timeouts, and a saga or outbox you shipped.
• Kubernetes and tracing ( OpenTelemetry or equivalent).
• Bachelor’s or Master’s in Computer Science, or equivalent practical depth.

Preferred

• Cosmos SDK, an EVM client, or a bridge audit you sat through.
• SDKs in more than one language, with a stranger able to run the example.
• Kafka or an equivalent log, if that is how you delivered events. Not required as a brand.
• A public artifact: a spec, a relayer, a crate, or a design doc.

Not persuasive on its own

• A claim of 1 million TPS, sub-50ms across 20 chains, or tens of billions of events a day. Bring a trace, a repository, or neither.
• A governance design in which THEO holders vote. THEO is a utility token. Autheo is not a DAO.

First 90 Days

• A written map of the API and bridge surface that is live versus stubbed, agreed with Protocol and SRE.
• One versioned gRPC or GraphQL contract in production or on a public test path, with a Go or Rust client and a JavaScript binding.
• One IBC or bridge flow with the timeout, the ack, and the trace.
• OpenTelemetry on that path, and a note on what the traces showed.
• A sandbox or docs page a DevHub user can finish without you on the call.

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. Interoperability is the contract those other systems call.

🌐 🚀 WHY JOIN LAUNCH LEGENDS?

• The chain is up. Staking, fees, DevHub, IBC, and four verified THEO markets are already public.
• The seat is the API and the packet , next to Protocol and SRE, not a slide about 20 chains.
• 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.