PATCHPAY — Code ships. Payment follows.

New bounty

Put the work — and the escrow — on record.

Bounty title *Detailed task description *What exactly needs to change, how it will be judged, test expectations. This is what developers work from.

GitHub repository *Format: owner/repo (public repo).Issue number Optional — links the bounty to a GitHub issue.

Required target branch *The PR must target this branch.Expected developer (GitHub) Optional — only this GitHub user can claim the bounty.

Reward (NEAR) *Locked in escrow on creation.Verification budget (NEAR) *Covers TEE execution fees. Unused budget is refunded.Submission deadline *After this, no new submissions; you may refund.

Acceptance conditions Optional — merged into the bounty description. Be specific: what counts as done?

What happens when you continue:

You review every field on the next screen.
You approve one transaction in your wallet: the reward + verification budget + storage fee move into the escrow contract.
The bounty goes live on the marketplace as Open.