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

Autheo is building a Cosmos-based Layer-0 coordination layer and integrated Layer-1 blockchain. The Senior Go Protocol Engineer will develop and maintain chain modules, IBC interoperability, and developer tooling, while testing and operating the network.

Responsibilities:

• Design, build, and review Cosmos SDK modules for Autheo’s staking and fee model, reward distribution, validator rules, and governance
• Write state migrations and upgrade handlers that are deterministic, tested, and rehearsed on testnet before they ship
• Keep the chain’s modules current with upstream Cosmos SDK, CometBFT, and IBC-Go releases
• Own IBC paths end to end: channel setup, transfers and memos, light-client and misbehaviour handling, and relayer operation (Hermes, the Go relayer, or equivalent)
• Work with the bridge and EVM teams so assets and messages move between Autheo’s execution environments with clear failure modes
• Build and maintain Go tooling builders actually use: CLIs, Protobuf and gRPC code generation, module scaffolding, and SDK migration tools
• Turn protocol changes into tooling and docs, so a developer can scaffold, test, and deploy on Autheo from DevHub without help
• Unit, simulation, and end-to-end tests for every module change; CI that builds, tests, and blocks a bad release
• Run what you ship: testnet nodes and validators, Kubernetes deployment, and Prometheus / Grafana dashboards that explain a failure without guesswork

Requirements:

• Public Go you wrote inside a blockchain codebase. Merged pull requests to Cosmos SDK, CometBFT, IBC-Go, a Cosmos SDK chain, go-ethereum, or an equivalent protocol repository. We read the code before we read the resume. Applications without a link to blockchain Go code you wrote yourself will not be reviewed
• 5+ years of production Go: concurrency, context cancellation, worker pools, batching, and performance problems you have debugged under load
• Cosmos SDK module work that shipped on a public network: keepers, message servers, genesis, state migrations, or upgrade handlers in staking, distribution, governance, or fee logic. Name the chain, the module, and your part in it
• Hands-on IBC: transfers, channels, light clients, misbehaviour handling, or relayer integration and operation. Link the change or the relayer setup you ran
• Developer tooling other engineers depend on: a CLI, code generator, Protobuf / gRPC pipeline, scaffolding, or SDK migration tool. Link the repository or release
• Comfortable operating your own work: Linux, Docker, Kubernetes, CI pipelines, full nodes or validators, and Prometheus / Grafana monitoring
• Maintainer or top-contributor status on a public blockchain repository
• EVM experience next to Cosmos: Cosmos EVM integration, Solidity contracts you deployed, or Go services calling contracts through ABI bindings
• Ethereum Layer 2 or zk-rollup engineering (transaction selection, proof submission, L2 signing)
• Wallet, custody, or signing infrastructure: key handling, hot / warm / cold wallet flows, multi-chain transaction tracking
• Multi-chain indexing or block-explorer back ends that you operated in production
• CosmWasm or Rust experience (a plus, not required)
• Teaching, conference talks, or workshops on blockchain engineering