Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
Saifuro LLC is hiring a Solidity developer to own on-chain escrow and verification systems. You will build and maintain contracts that hold funds securely, verify signatures on-chain, and prepare for audits and releases with deployment scripts and recovery playbooks.
The role includes expanding to additional EVM chains and milestones, with a strong emphasis on security, reliability, and scalable architecture at pace.
Saifuro checks payments that AI agents try to make. An agent asks to spend, we compare the request with a mandate a human approved earlier, and the answer comes back signed so the receiving side can verify it. There's escrow on Base and Solana for trades between agents, and settlement is in USDC, onchain. We never hold customer funds. The docs are public at docs.saifuro.com, and the people who use them are developers building agents and the teams selling APIs to those agents.
The escrow is the one place where our code holds other people's money. Funds go in, sit until a signed verdict says the deal is done, and come out to the seller or back to the buyer, with no path in which Saifuro can move them. Your job is to own the EVM side: the escrow, the verifier that checks our signatures onchain, the audits and the deployments. Call it Solidity developer, smart contract developer or blockchain developer if you prefer. It's Solidity first.
Beyond these requirements, we’ll support you in learning whatever else the role demands. If your experience is relevant but your title differs, we would still like to hear from you. Work outside a job counts too: open source, hackathons and your own projects.
It helps, but isn’t required, if you know storage layout, reentrancy and signature verification at the EVM level, if you’ve written Rust or Anchor programs on Solana, if you’ve worked with account abstraction (ERC-4337) or session keys for agents, if you know Circle’s USDC contracts and CCTP, if you’ve found bugs for a bounty or did security research, or if your work is open source.
Hours are flexible. The one thing we ask is to be online from 14:00 to 17:00 UTC, when the team overlaps for calls and quick questions. That’s a window, not the working day. The rest of your hours are yours to arrange. A mainnet incident doesn’t keep office hours. If that window is the middle of your night, say so and we’ll work something out.
You can combine this with a job at another company, as long as the two don’t conflict and nothing you’d write there touches our contracts or competes with them.