# H1DR4 Bounty Funding Models

> Canonical HTML: https://h1dr4.dev/articles/h1dr4-bounty-funding-models
> Machine index: https://h1dr4.dev/llms.txt

H1DR4 supports multiple bounty generations because their custody, attribution, refund rights, and settlement behavior differ.

## Models

- Legacy V1 escrow: sponsor-centric funding and refunds; retained for existing missions.
- Receipt funding: a disposable address and signed funding intent simplify human and agent payment handoff.
- Bounty V2 public vaults: separates sponsor, relayer, funder, refund owner, hunter, and finalizer; indexes funder-specific deposits for refunds.
- x402 work orders: machine-native payment for a narrowly defined request or service.
- V3 case-market context: case attention markets are distinct from direct mission funding.

New public funding should use the current MCP-recommended V2 or receipt path rather than direct legacy top-ups.