Free tool · ordinary software bounties only
Check the payout evidence before you write the code.
A dollar amount in a listing is not proof of funding. Use eight hard checks and a paid-case return calculation to separate a work-ready coding bounty from a HOLD or NO-GO.
No login · No tracking · No form submission · Inputs remain in your browser
- Funds reserved now
- verify
- Acceptance authority
- verify
- Claimant spend
- $0
- Paid-case return
- calculate
rule missing evidence stays unknown
Browser-only worksheet
Evaluate one public coding bounty.
Confirm only what the public evidence proves. Leaving a box unchecked means unknown—not false. The tool stores and sends nothing.
- 01
Funding exists now
An advertised reward is marketing. Escrow, a reserved processor balance, or job-specific on-chain funds are evidence.
- 02
Authority is explicit
Name who can accept delivery, reject it, release payment, resolve disputes, and change the deadline.
- 03
The paid case survives costs
Subtract known fees and divide by bounded labor hours. Call that paid-case hourly return—not expected value.
- 04
Unknown stays unknown
Competition, asset liquidity, rights, or acceptance gaps do not become favorable assumptions because the headline reward is large.
- 05
Worker-funded claims stop
A required deposit, bond, purchase, transfer, or trade changes a zero-capital job into a spend decision and a separate risk.
- 06
Scope stays ordinary
This checklist is for lawful software, documentation, data, design, and integration work—not vulnerability research or security testing.
Worked public-evidence example
$399 advertised. $0.084841 available.
Two public listings advertised $250 and $149 from the same buyer. The buyer address held 0.084841 USDC, the platform said there was no escrow and payment followed delivery, public legal routes were absent, and prior completed records exposed no payout proof.
- 01
Headline reward
$399 across two listings looked attractive before funding was checked.
- 02
Buyer funds
0.084841 USDC could not fund either advertised job.
- 03
Delivery protection
No escrow meant the worker would deliver before any documented settlement.
- 04
Decision
NO-GO. A proposal would not repair missing funds, legal allocation, or payout history.
Public source examples
Good platforms make payment protection inspectable.
These third-party sources are examples, not endorsements. Apply each platform’s current rules to that platform only.
Open the reusable Red-Flag CardCommon decisions
Direct answers.
Do I need a GitHub account?
No GitHub account required. The worksheet runs entirely in this page; only the optional paid-review intake offers GitHub and business-email routes.
Is an on-chain balance the same as escrow?
No. A wallet balance may show capacity, but it does not prove that funds are reserved for your job or that you can release them. Verify the exact payment mechanism.
What if every check passes except acceptance criteria?
HOLD. A funded reward without an objective passing condition can still become unpaid work.
Does GO guarantee payment?
No. GO means the public evidence clears the stated gates at the cutoff. It is not a payout, profit, or outcome guarantee.
Does the worksheet save my bounty details?
No. It has no submission endpoint, analytics call, storage API, cookie, or account requirement. Resetting or closing the page clears the inputs.
Can this be used for bug bounties?
No. WrightOps does not provide vulnerability research, exploitation, security testing, or security-bounty guidance. This page is for ordinary software work.
One listing · public evidence · bounded decision
Still missing the fact that changes the decision?
The $49 WrightOps review checks one public coding bounty and returns an evidence-linked GO, HOLD, or NO-GO report. Scope is confirmed before payment, and work starts only after settlement.
Operational information only · Not legal, tax, financial, investment, security, privacy, or compliance advice