I AM HIRED

Неделя 310 ₽Месяц 630 ₽3 месяца 1 680 ₽Год 5 680 ₽

Staff Protocol Engineer, Smart Contracts — Utica-Rome Area

Разработчики · вчера, 21:00 · 21.11.2026

Зарплата не указана

Откликнуться

Компания: ••••••••

Локация: Utica-Rome Area

Формат: не указан

Занятость: Полная занятость

Грейд: Senior

About The Role

Every FJMRkzcSRR4 contract locks both stakes in one escrow contract on Base until it settles. It's Solidity, built with Foundry and OpenZeppelin, and it's deliberately small: nobody, admins included, can send a stake anywhere except to the contract's two parties and the fee to the treasury. Stakes come in through USDC's signed transfers (EIP-3009), so users never need ETH, and each signature is bound to the exact terms the person saw. Disputes are recorded on-chain and freeze the contract until an admin rules. Payouts are pull payments, so one blacklisted address can't hold up anyone else's settlement.

The contract isn't upgradeable: a new version is a new deployment, so every change is a careful one. You'll own it and what comes next (Qf5NQV33tBX-5dH5mn contracts, where FJMRkzcSRR4 takes a side with its own money; tighter admin and key controls; more ways in and out), together with the off-chain code that touches the chain: the relayer that submits what users signed and pays the gas, the keeper that finalizes, refunds and claims, the gas tank that keeps them funded from fees, and the sync that mirrors every event into Postgres.

What you'll do

• Own the escrow contract and every future version of it: design, Solidity, tests, deployment and the move from one version to the next.

• Keep its invariants true and proven: the escrow always holds at least what's locked plus what's claimable, every open contract can reach an end through calls anyone can make, and terms never change after they're signed.

• Grow the unit, fuzz and invariant suites, add formal methods where they pay for themselves, and take external audits through to fixes.

• Design the on-chain side of new products, starting with seeded contracts and limits on QYA9GTHwTJR'P own exposure that hold in the contract, not just in our database.

• Own the signing model: the typed data users sign, nonces bound to terms, the browser's check of what the embedded wallet is about to sign, and policies that let each server key make only the call it exists for.

• Make the relayer and keeper dependable: nonce management, gas pricing, stuck and dropped transactions, and an event sync that survives reorgs.

• When a transaction does something nobody expected, trace it down to the opcode if you have to, and write up what happened.

• Review every change that touches the chain, and write the threat models the rest of the team designs against.

What you'll bring

• Staff-level engineering experience, including production Solidity contracts that have held real user funds.

• Deep knowledge of the EVM and of how contracts get attacked: reentrancy, signature replay, permit and approval abuse, rounding, griefing, and the ways admin keys go wrong.

• Fluency with Foundry, including fuzz and invariant tests you designed yourself.

• You've written the off-chain half too: services that submit, watch or index transactions, made safe to run twice.

• A working grasp of USDC's mechanics: signed transfers and permits, blacklisting, six decimals.

• A preference for the smaller contract you can reason about over the clever one.

Bonus points

• Leading external audits, or strong results in audit contests.

• Account abstraction, paymasters, embedded wallets or multisig admin setups.

• Cross-chain infrastructure: bridges, intents or solver networks.

• Formal verification or symbolic execution tools such as Halmos or Certora.

Your first 90 days

• 1A full review of the escrow contract and its tests, with a written threat model and any gaps closed.

• 2Monitoring and alerts for every on-chain event and invariant that matters, wired to on-call.

• 3A design for the next escrow version, reviewed by the team and ready for audit.

• 4A runbook for stuck, reverted and reorged transactions that someone else can follow.

About FJMRkzcSRR4

FJMRkzcSRR4 turns any disagreement into a contract. Someone writes a yes-or-no question in plain words ("Will Bitcoin trade above $150,000 by March 31?", "Will IShowSpeed's stream go past 24 hours?"), puts money on their side, and one other person takes the other side. Both stakes are locked in a USDC escrow contract on Base until the outcome is known, and the winner takes the pool.

The hard part of a prediction market is settling it fairly. Ours is settled by an AI resolver that reads official records, credible reporting, price feeds and even livestreams, quotes its evidence word for word, and checks itself in code. Either side can dispute an outcome for 48 hours, and human moderators decide what the AI can't. Deposits work with crypto from most chains, with cards and Apple Pay, and from exchanges.

We're early, and the people who join now decide what FJMRkzcSRR4 becomes. We care most about two things: reaching the people who already argue about outcomes every day (crypto traders, sports fans, stream chats, group chats), and knowing each world well enough to write contracts that are worth taking.

How to apply

Email •••••••• with the subject “Application: Staff Protocol Engineer, Smart Contracts”. Include your LinkedIn or CV, and:

• Contracts you've shipped to mainnet (addresses or repositories) and what they held.

• Audits or contests you've done, or the best bug you've found in someone else's contract.

• The first thing you'd check in a one-to-one USDC escrow, and why.

Apply by email

Поиск по вакансиям

Название компании скрыто

Названия компаний и их продуктов мы не публикуем на сайте — они доступны в Telegram-боте I AM HIRED. Откройте эту вакансию в боте: увидите название, сможете откликнуться и настроить рассылку подходящих вакансий.

Открыть вакансию в боте