Xsolla is a global commerce company with robust tools and services to help developers solve the inherent challenges of the video game industry. From indie to AAA, companies partner with Xsolla to help them fund, distribute, market, and monetize their games. Grounded in the belief in the future of video games, Xsolla is resolute in the mission to bring opportunities together, and continually make new resources available to creators. Headquartered and incorporated in Los Angeles, California, Xsolla operates as the merchant of record and has helped over 1,500+ game developers to reach more players and grow their businesses around the world. With more paths to profits and ways to win, developers have all the things needed to enjoy the game.
For more information, visit xsolla.com.
О роли
We are hiring a Staff Software Engineer to own the smart wallet and account abstraction layer of Xsolla ZK, Xsolla's Web3 platform on a zkSync-based L2. This is an individual contributor role with a large technical scope. You are the technical anchor for how millions of players get an on-chain account they never have to think about.
The product. Every player who signs in with Xsolla ID receives a deterministic, non-custodial smart account. The account is derived from their identity claim, is identical on every device, and its private keys never leave the client. It is not a separate wallet screen: it is the player's inventory. It backs:
minting and gifting;
trading on our Bazaar marketplace;
Merkle-based reward airdrops;
gas sponsorship;
an in-app dApp browser that exposes the same signer to third-party applications through an EIP-1193 provider.
Обязанности
The technical strategy and architecture of the smart wallet platform: account model, signing, session management and gas abstraction at scale
The smart account and permissioning model, evolved to meet both product and compliance needs
The security model where our signer meets third-party applications: what a player is actually approving, and proof that the UI shows it
The custody and recovery roadmap, from today's interim mechanisms (including raw key export) to MPC-based custody
Cross-team technical decisions on account architecture, SDK contracts, data modeling and platform reliability, with buy-in from the wallet, marketplace, SDK, mobile and security teams
Engineering standards in the Web3 domain
Production escalations in the wallet and account abstraction domain
Что предстоит делать
Design and evolve the ERC-4337 user operation lifecycle (prepare → sign → submit → confirm), EIP-7702 delegation, deterministic address derivation from identity, and the session-key and permission primitives (including origin-bound Smart Sessions) that let players act without a prompt on every transaction
Set the paymaster and gas-sponsorship strategy: what we sponsor, how we meter and cap it, how we defend it from abuse, and how it degrades when sponsorship is unavailable
Define EIP-1193 / EIP-6963 provider behavior, origin-bound and policy-versioned sessions, trust tiers, and the transaction and signature confirmation flow
Design recovery paths (passkeys, guardians, social recovery) that a non-crypto-native player can complete without losing assets
Identify systemic risks (key management, signature phishing, reorgs and indexer staleness, bundler and RPC dependencies, contract upgrade paths) and lead initiatives that resolve them before they become incidents
Write RFCs and design docs; review critical code, contracts and designs
Work with product, security, legal and infra teams to align on the roadmap and turn business and regulatory needs into well-scoped technical plans
Create leverage for the engineering org through documentation, tooling and mentorship
Serve as the escalation point for complex production issues: a stuck user operation, a drained paymaster, a signing prompt a player didn't understand
Set up and maintain AI tooling in the repositories (Claude Code, Codex, Cursor: rules, context, harness) so the team uses it effectively
Обязательно
Experience
8+ years of engineering in the Ethereum ecosystem working with crypto wallets and smart wallets
Designing or operating a production smart wallet or account abstraction system serving real users and real value
Shipping and operating systems where a bug meant lost funds. You can talk concretely about the guardrails, reviews and rollback paths you put in place
Account abstraction and smart wallets
ERC-4337 in depth: EntryPoint (v0.6 through v0.8), the UserOperation lifecycle, bundler and paymaster roles, validation rules (ERC-7562), gas estimation and its failure modes, counterfactual deployment, signature validation for undeployed accounts (ERC-6492)
EIP-7702 and the post-Pectra landscape: EOA delegation, its interaction with EntryPoint v0.8, and the risks it introduces (residual key authority, delegation phishing, storage collisions)
Building on or extending production smart account implementations; modular account standards (ERC-7579 / ERC-6900)
Session keys and delegated permissions: scoped, time-limited, policy-bound authority; TTLs and contract allowlists, origin binding, permission revocation; ERC-7710 / ERC-7715
Solidity and the EVM: reading, reviewing and writing account, paymaster and module contracts; gas-aware design; upgradeability and migration patterns; working effectively with external auditors
L2 specifics and their effect on wallet design: native account abstraction on zkSync-family chains, transaction and fee models, finality and reorg behavior, RPC and indexer semantics
Backend…
Текст вакансии длинный, здесь показана его часть. Полностью — на сайте студии.
В этой вакансии студия требует право работать в своей стране — гражданство, вид на жительство или рабочую визу. Даже если указана удалённая работа, кандидата из другой страны обычно не рассматривают. Проверьте условия в оригинале перед откликом.
Отклик принимает студия на своём сайте. LOOTWORK только показывает вакансию.