Head of Trading Systems / Matching — Autheo Spot & Perpetual Venue | Order Book, Latency & Settlement

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


• 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 has been live since May 14, 2026. 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. The venue you will build is not.

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. MEXC serves more than 40 million users across more than 170 countries and regions. 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, pairing THEO with a Robinhood Stock Token. Official Robinhood Chain contract: 0x3dc751e0da01812e6d9143cc696e7f07ea94da48

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

Those are external markets. This seat does not run them.

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. 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: Head of Trading Systems / Matching — Autheo Spot & Perpetual Venue | Order Book, Latency & Settlement

About the Role

Autheo is recruiting the person who will build the matcher.

THEO already trades on MEXC, Hydrex, and Uniswap on Robinhood Chain. That book is not yours. A separate seat, VP of Exchanges & Token Markets, owns those external listings and the next ones. A second seat, Head of Markets / DEX GM, owns the venue as a product and a P&L: listing policy, fees, maker program, insurance fund, and the architecture decision. You report into that GM. You do not replace them.

You design and ship the trading system: central limit order book, matching, cancel/replace, self-trade prevention, time-in-force, funding ticks, the liquidation handoff, and the path from a matched trade to settlement on Autheo. The comparable engines are Hyperliquid’s on-chain book, Lighter’s zk-proven matcher, and dYdX v4’s validator-run matching. The underlyings are not only crypto. V1 has to carry THEO spot, two to three crypto perps, one infrastructure future, one RWA, and one agent-credit or agent-SLA market. If the engine can only price BTC, it is the wrong engine.

The GM picks the architecture in week one. The rational first choices are validator-run matching on Autheo’s Cosmos stack, or an off-chain matcher with proofs settling on the Autheo EVM. A native CLOB is on the table only if you can carry it. Deploying markets on someone else’s engine is a go-to-market tactic, not this job.

This is a systems seat. Rust or Go. Not a Solidity role with a matching diagram attached.

Key Responsibilities

• Build the matching engine: price-time priority, or the priority model the GM signs, with deterministic behavior under cancel races


• Specify and ship order types for v1: limit, market, post-only, IOC, GTC, and the cancel/replace path a market maker will actually use


• Set the latency budget and measure it. Median, p99, and what happens when the book is under load. A number you cannot reproduce is not a number


• Implement self-trade prevention, sequence numbers, and a fairness rule you can explain to a market maker in one page


• Own the funding tick, mark-price input, and the handoff into liquidation. You do not own margin math or the insurance fund. Head of Risk, Clearing & Oracles owns those. You own the engine that calls them on time


• Settle matched trades on Autheo: native module, Cosmos sidecar, or proof plus EVM settlement, per the architecture decision. IBC and the EVM environment are already there. Do not invent a second chain to avoid them


• Design the state model so an infrastructure future, an RWA perp, and an agent-credit market can list without a rewrite. Oracle inputs are the risk seat’s problem. Consuming them without stalling the book is yours


• Publish a failure spec: sequencer stall, proof lag, validator halt, clock skew, duplicate cancel, crossed book. Each one gets a behavior, not a hope


• Instrument the book: order-ack time, cancel-ack time, match rate, reject reasons, and a replay log that can reconstruct a session


• Hire or designate the first two engineers under this seat only after the spec is written. A team without a matching spec is a club

Requirements — Must Have

• Has shipped a live matching engine, or the core of one, on a venue with real orders. A backtest and a whitepaper do not count


• Can defend price-time priority, cancel/replace, self-trade prevention, and sequence gaps on a whiteboard without notes


• Writes the hot path in Rust or Go. Solidity is acceptable for settlement, not for matching


• Has operated a latency budget under load and can show the measurement, not the target


• Understands how a perp funding tick and a liquidation handoff sit next to the matcher, even if someone else owns the risk formula


• Will take an architecture decision from the GM — validator-run, zk-proven off-chain, or native CLOB — and implement it, rather than reopen it every week

Nice to Have

• Time on a Hyperliquid, Lighter, dYdX, Injective, Sei, or Osmosis trading system, or on a Jump, Wintermute, HRT, or Citadel crypto execution stack


• Cosmos SDK module experience, CometBFT, or a zk proof pipeline used for matching or state commitments


• Built a replay and deterministic-simulation harness for an order book


• Familiarity with non-crypto underlyings enough to keep oracle reads off the match path


• Post-quantum signature verification costs, if TheoID key material ever sits on the order path. It should not sit on the hot path in v1

First 90-Day Deliverables

• Matching spec: priority, order types, cancel/replace, self-trade prevention, sequence numbers, and the reject table


• Latency budget with a measurement method, and a first number from a test harness, not a slide


• Settlement design against the chosen architecture, written to Autheo L1, not to a generic chain


• Failure spec covering stall, proof lag, duplicate cancel, and crossed book


• Replay log format sufficient to reconstruct one session trade for trade


• A working testnet matcher on THEO spot and one perp, with the liquidation handoff stubbed to the risk seat’s interface

About Our Organization

Autheo is building the Internet operating system: a decentralized coordination layer for the Web, blockchain, and AI agents. The platform uses W3C Decentralized Identifiers as its native identity framework and is anchored by a post-quantum communications and identity roadmap on NIST-standardized cryptography. Operating alongside a sovereign Cosmos-based Layer-0 and an EVM-compatible Layer-1, Autheo is designed so applications, infrastructure, and agents settle in one system rather than five vendor stacks.

The economic layer is already open. THEO trades on MEXC, on Hydrex on Base, and on Uniswap on Robinhood Chain. The next market is the one Autheo matches itself.

WHY JOIN LAUNCH LEGENDS?

• The coin is already listed. MEXC opened October 1, 2026. Hydrex and Robinhood Chain were already live. You are not building a matcher for a token that has never traded.


• The engine does not exist yet. External venues are someone else’s book. This seat is the book Autheo will run.


• A GM above you, a risk seat beside you. You will not be asked to set fees, recruit market makers, and design the insurance fund in the same week. You will be asked to make the match deterministic.


• Equity cofounder, not a contractor seat. You join the same model as the rest of the collective: equity in Launch Legends, Autheo, and the WFO Creator Network, plus THEO allocation, with salary expected to follow node, token, or funding milestones.

If you have shipped a matcher, can say what a cancel does under load, and would rather write the engine than the listing announcement, we invite you to take the next step.

Let’s build the book—on the network that is already live.