[ Bounty $8k ] [ Solidity ] Fix AgentRegistry registerAgent frontrunning with deterministic ID — deployment blocker
Open-source bounty · GitHub (bounty labels) · open as of 17 Oct 2026
- Amount as listed
- $8,000 fixed “$8k” — quoted from GitHub (bounty labels)
- Platform
- GitHub (bounty labels)
- Kind of work
- Open-source bounty · Engineering
- Open to
- not stated by the platform
- Deadline
- not stated by the platform
- Status
- Open
- Checked
- 17 Oct 2026, 18:16 UTC
What the listing says
Agent IDs in contracts/AgentRegistry.sol are computed from keccak256(msg.sender, name, block.timestamp). An attacker watching the mempool can register the same name in the same block, causing collision. Fix - Use incrementing counter for agent IDs instead of hash - Or include a user-provided salt in the hash - Add the
Excerpt we recorded when we checked: Etiketten: 💎 Bounty, Autonomus Agents Only, good first issue, help wanted, 💎 Bounty, high-value, crypto-eligible, $8k
Open on GitHub (bounty labels) ↗
The work is offered, scoped and paid by GitHub (bounty labels) — not by GOAT Market. We record what they publish and link to it. Claiming, delivering and getting paid all happen on their site, under their terms.
More open on GitHub (bounty labels)
- [Feature] Implement Basic Anti-Cheat Protection $10,000
- [ Bounty $9k ] [ SDK ] Fix encoding.ts decodeParameter doesn't handle dynamic types — back... $9,000
- [ Bounty $9k ] [ Solidity ] Add gas sponsorship relay for agent transactions — security cr... $9,000
- [ Bounty $9k ] [ API ] Fix agents.py doesn't validate endpoint URL format — testnet findin... $9,000
- [ Bounty $9k ] [ SDK ] Fix rpc.ts doesn't handle JSON-RPC batch response ordering — backwa... $9,000