A complete application in a minute
Tailored resume and cover letter, ready to send.
Saifuro LLC is hiring a Solana developer to build and maintain the escrow program and on-chain verifier in Rust. You will contribute to audits, ensure cross-chain parity, and implement secure settlement logic for USDC transfers.
The role supports developers building agents and API integrations. Flexible hours are offered within a structured UTC overlap window, with remote-friendly options in eligible countries.
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. USDC goes in, waits until a signed verdict says the deal is done, and comes out to the seller or back to the buyer, with no path in which Saifuro can move it. On Solana that's an Anchor program, and it would be yours: the program, the check on our signatures, the audits and the releases. Call it Solana developer, smart contract developer or Rust developer if you prefer. It's Rust.
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 how a program gets drained when a signer or owner check is missing, if you've written Solidity, if you know the SPL Token and Token-2022 programs, if you've worked with USDC on Solana or Circle's CCTP, if you've found bugs for a bounty or done 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 programs or competes with them.