Planned change
Add a public, additive KeeperHub execution adapter, an operator guide, and deterministic tests so an agent can prepare an Agent Bounties onchain action, execute it through KeeperHub, monitor it, and retain a canonical receipt for the KeeperHub Agents Onchain Hackathon.
Why
The current product already supports public bounty discovery, deterministic verification, Base USDC settlement, and bounded agent wallets. The hackathon integration needs KeeperHub to be the explicit last-mile onchain execution layer, with truthful evidence of an actual KeeperHub transaction.
Likely scope
- New KeeperHub-specific script(s) under
scripts/
- New public integration guide under
docs/
- New isolated tests/fixtures for request validation, simulation-first behavior, idempotency, status monitoring, and receipt handling
- No smart-contract, escrow, canonical-event, payout, existing API, MCP, SDK, or database migration changes
Open contributor queue
Checked all 87 open pull requests before starting. Forty have activity in the last three days and 23 non-maintainer authors are represented. The newest active work is concentrated in MCP protocol membership, inventory counts, Base RPC failover, Hermes/OpenHands integrations, and dependency updates.
Contributor impact
None known. This slice will use new, KeeperHub-specific files from a clean origin/main worktree. It does not supersede, close, relabel, or rewrite any contributor PR. Existing bounties, contributors, claims, funding, settlement evidence, and payments remain unchanged.
Repair or migration path
No migration is expected. If an overlapping public-integration document is identified during review, the maintainer branch will rebase and move the KeeperHub material into a dedicated document rather than forcing contributor rework. No collaboration branch is currently recommended because no open PR is being superseded.
Release boundary
Source and dry-run validation can land independently. Public readiness requires a real KeeperHub execution receipt and exact monitoring evidence. Only a confirmed canonical BountySettled event may be described as solver payment. This notice is not merge approval, bounty acceptance, payout approval, or settlement.
Distribution feedback
- How did you find Agent Bounties?
- What made this bounty or project worth participating in?
- Did an AI agent, tool, prompt, link, label, scanner, or workflow route you here?
- What would make participation easier or more trustworthy?
If this work is useful, please star the repository, react to useful bounties, and share it with agent builders or bounty solvers.
Planned change
Add a public, additive KeeperHub execution adapter, an operator guide, and deterministic tests so an agent can prepare an Agent Bounties onchain action, execute it through KeeperHub, monitor it, and retain a canonical receipt for the KeeperHub Agents Onchain Hackathon.
Why
The current product already supports public bounty discovery, deterministic verification, Base USDC settlement, and bounded agent wallets. The hackathon integration needs KeeperHub to be the explicit last-mile onchain execution layer, with truthful evidence of an actual KeeperHub transaction.
Likely scope
scripts/docs/Open contributor queue
Checked all 87 open pull requests before starting. Forty have activity in the last three days and 23 non-maintainer authors are represented. The newest active work is concentrated in MCP protocol membership, inventory counts, Base RPC failover, Hermes/OpenHands integrations, and dependency updates.
Contributor impact
None known. This slice will use new, KeeperHub-specific files from a clean
origin/mainworktree. It does not supersede, close, relabel, or rewrite any contributor PR. Existing bounties, contributors, claims, funding, settlement evidence, and payments remain unchanged.Repair or migration path
No migration is expected. If an overlapping public-integration document is identified during review, the maintainer branch will rebase and move the KeeperHub material into a dedicated document rather than forcing contributor rework. No collaboration branch is currently recommended because no open PR is being superseded.
Release boundary
Source and dry-run validation can land independently. Public readiness requires a real KeeperHub execution receipt and exact monitoring evidence. Only a confirmed canonical
BountySettledevent may be described as solver payment. This notice is not merge approval, bounty acceptance, payout approval, or settlement.Distribution feedback
If this work is useful, please star the repository, react to useful bounties, and share it with agent builders or bounty solvers.