poidh Degen collected claim NFTs

Every collected claim NFT on Degen Chain — both contract versions — read straight from the chain.

Download CSV (736 rows) Source & scripts on GitHub

What this is

Built for poidh Base bounty #364, which asked for a CSV of every collected poidh claim NFT on Degen Chain. "Collected" = the claim NFT has left the poidh escrow contract and is held by a real wallet (i.e. the claim was accepted). Both Degen deployments are covered:

• v3 — NFT 0x39F04b7897DCAf9Dc454E433F43Fb1C3bB528E11, escrow 0x18E5585ca7cE31b90Bc8BB7aAf84152857cE243f
• v2 — NFT 0xDdfb1A53E7b73Dba09f79FCA24765C593D447a80, escrow 0x2445BfFc6aB9EEc6C562f8D7EE325CddF1780814

Columns

One row per collected NFT:

• title — claim title
• description — claim description
• image_url — the claim image (IPFS, via the token's own tokenURI metadata)
• claim_id — on-chain claim / NFT token id
• holder_wallet — wallet that currently holds the NFT
• bounty_name, bounty_description — the bounty the claim answered
• bounty_creator_wallet — wallet that created that bounty
• contract_version, nft_contract — v2 or v3, and the NFT contract address

Method — nothing rests on a third-party index

• Which NFTs are collected: replay every ERC-721 Transfer log for each NFT contract from deployment to head, over rpc.degen.tips, to get the current holder of every token id; keep those whose holder is not the zero address or the escrow contract.
• Titles, descriptions, source bounty: joined from the contracts' own ClaimCreated / BountyCreated event logs. The 17 earliest v2 claims (ids 0–16) predate the event and are read directly from the claims(id) getter.
• Image URLs: resolved live from each token's on-chain tokenURI, then the metadata document's image field.

A Blockscout index silently drops 17 v2 claim logs (it reports 4,516 of 4,533); the raw RPC sweep here does not, which is why all 17 early claims are present.

Preview (first 60 rows; full data in the CSV)