Senior Go Protocol Engineer — Autheo | Cosmos SDK Modules, IBC & Chain Developer Tooling

Launch Legends•Cheyenne, WY

1d•Remote

About The Position

Launch Legends and Autheo are seeking a senior Go engineer to build and maintain protocol code for Autheo’s Cosmos-based Layer-0 coordination layer, IBC interoperability, and EVM-compatible execution environment. This is a hands-on engineering role reporting to the engineering leads. The engineer will own changes from design through upgrade and build developer tooling that helps teams get started on Autheo. The role includes designing and reviewing Cosmos SDK modules for staking, fees, rewards, validator rules, and governance; implementing deterministic state migrations and upgrade handlers; and keeping modules current with Cosmos SDK, CometBFT, and IBC-Go. It also owns IBC paths and relayer workflows, works with bridge and EVM teams on cross-environment asset and message movement, and develops CLI, Protobuf/gRPC, scaffolding, and migration tools for DevHub. The engineer will create unit, simulation, and end-to-end tests, maintain CI safeguards, and operate testnet nodes and validators, Kubernetes deployments, and Prometheus/Grafana monitoring. The first 90 days include reviewing the Cosmos SDK modules and IBC setup, shipping a module change or upgrade handler through testnet rehearsal, documenting and owning an IBC path or relayer workflow, and delivering a DevHub tooling improvement used by another team. This is a part-time equity- and token-based cofounder opportunity requiring at least 20 hours per week. There is no cash salary. Compensation includes equity in Launch Legends, Autheo, and the WFO Creator Network, plus Autheo blockchain token allocations. The position is remote.

Requirements

At least 5 years of production Go experience, including concurrency, context cancellation, worker pools, batching, and performance debugging under load.
Public Go code personally written in a blockchain codebase; provide links to code. Applications without a link to blockchain Go code written by the applicant will not be reviewed.
Merged pull requests to Cosmos SDK, CometBFT, IBC-Go, a Cosmos SDK chain, go-ethereum, or an equivalent protocol repository.
Cosmos SDK module work shipped on a public network, involving keepers, message servers, genesis, state migrations, or upgrade handlers in staking, distribution, governance, or fee logic; applicants should identify the chain, module, and their contribution.
Hands-on IBC experience with transfers, channels, light clients, misbehaviour handling, or relayer integration and operation; provide a link to the change or relayer setup operated.
Experience building developer tooling used by other engineers, such as a CLI, code generator, Protobuf/gRPC pipeline, scaffolding, or SDK migration tool; provide a repository or release link.
Ability to operate own work using Linux, Docker, Kubernetes, CI pipelines, full nodes or validators, and Prometheus/Grafana monitoring.
Availability for at least 20 hours per week.

Nice To Haves

Maintainer or top-contributor status on a public blockchain repository.
EVM experience alongside Cosmos, such as Cosmos EVM integration, deployed Solidity contracts, or Go services calling contracts through ABI bindings.
Ethereum Layer 2 or zk-rollup engineering, including transaction selection, proof submission, or L2 signing.
Wallet, custody, or signing infrastructure experience, including key handling, hot/warm/cold wallet flows, or multi-chain transaction tracking.
Experience operating multi-chain indexing or block-explorer back ends in production.
CosmWasm or Rust experience.
Teaching, conference talks, or workshops on blockchain engineering.

Responsibilities

Design, build, and review Cosmos SDK modules for staking, fees, reward distribution, validator rules, and governance.
Write deterministic, tested state migrations and upgrade handlers, and rehearse them on testnet before release.
Keep chain modules current with upstream Cosmos SDK, CometBFT, and IBC-Go releases.
Own IBC paths end to end, including channel setup, transfers and memos, light-client and misbehaviour handling, and relayer operation.
Coordinate with bridge and EVM teams so assets and messages move between Autheo execution environments with clear failure modes.
Build and maintain developer tooling, including CLIs, Protobuf and gRPC code generation, module scaffolding, and SDK migration tools.
Turn protocol changes into tooling and documentation that enable developers to scaffold, test, and deploy on Autheo through DevHub.
Write unit, simulation, and end-to-end tests for module changes and maintain CI that builds, tests, and blocks bad releases.
Operate testnet nodes and validators, Kubernetes deployments, and Prometheus/Grafana dashboards.
Review Autheo’s Cosmos SDK modules and IBC setup, identifying current status, upstream lag, and risks.
Ship at least one module change or upgrade handler through testnet rehearsal with simulation and end-to-end tests during the first 90 days.
Document, monitor, and own an IBC path or relayer workflow end to end during the first 90 days.
Deliver a DevHub tooling improvement, such as a scaffold, code generator, or CLI command, that another team uses during the first 90 days.