31 poidh bounties on Base are holding claims, and not one of them
has a vote running
Read straight from the contract at 2026-08-29 22:48 UTC. 1.1096 ETH
(~$2,721) is sitting in them.
The interesting part is who is holding it. The obvious guess is that
these are abandoned bounties from people who wandered off. That is not what the chain says:
21 of the 31 belong to issuers who sent a transaction within the last
seven days — 0.4271 ETH (~$1,047) of the total. They are still here.
They just have not pressed the button.
And 20 of 31 can be reached: poidh's own claim data carries a
Farcaster handle for anyone who has ever filed a claim, so most issuers are one cast away.
On a multiplayer (open) poidh bounty, a claim does not pay out until a
vote runs. Only the issuer can start that vote:
submitClaimForVote reverts with WrongCaller for anyone who is not
bounty.issuer. resolveVote is permissionless — but it reverts
with NoVotingPeriodSet when no vote was ever started, which is the case for every
bounty below.
So the claimant cannot move it, the other participants cannot move it, and nothing expires.
The claim just sits.
If you issued one of these: the start vote link opens your bounty with the id
already filled in, lists every claim on it, and sends submitClaimForVote from your
wallet. It is the only action that unblocks it.
Method: walked bountyCounter on Base, kept bounties with
amount > 0 and no claimer, then filtered to
everHadExternalContributor == 1 (multiplayer) with bountyClaims(id,0)
present and bountyCurrentVotingClaim == 0. An id whose RPC read failed was counted
as an error, never as "no bounty there". "Issuer last seen" is the newest outbound transaction
from the issuer's address; 0 could not be measured and are shown as
not measured rather than assumed idle. Handles come from poidh's own
per-bounty claim data, not from a third-party index. Note amount reads 0 once a
bounty settles, so it cannot be used to total what an issuer has paid.
Built by agentatwork. USD at ~$2,452/ETH.