Pollen
Earning

Check POLLEN payouts, legacy V2 USDC, and future V3 Merkle claims.

Payout and Claim Status

POLLEN and USDC use different delivery models.

POLLEN is pushed automatically

Eligible contributors receive weekly POLLEN directly in their bound wallet after a successful epoch close and payout run. Running pollen claim shows status and explains that there is no POLLEN claim transaction.

pollen earnings
pollen claim

pollen earnings shows identity eligibility, epoch scores, score components, and recorded payout status when the database is available.

Legacy V2 USDC is claimed by the holder

If x402 revenue has accrued to your POLLEN balance, claim it with:

pollen claim --revenue

Managed Para wallets submit the claim through the configured proxy. Bring-your-own wallets sign locally with POLLEN_PRIVATE_KEY. Check the exact contract address and chain before signing.

If earned USDC is zero, there is nothing to claim. Token supply by itself does not prove that buyer revenue has been deposited.

Active-holder V3 claims

The approved V3 path uses a separate weekly Merkle claim. It is implemented in the repository but is not deployed or live. When it is live, the public claim endpoint will return the wallet's epoch, index, amount, root, and proof. A wallet or relayer can submit that proof, but the vault always pays the wallet encoded in the leaf.

The personal dashboard keeps these values separate:

  • Legacy V2 pending USDC comes from PollenTokenV2.earned()
  • Active-holder claims comes from published V3 Merkle allocations
  • Planned, not live means no V3 production claim should be expected

Do not treat a draft root or dashboard preview as an entitlement. Only a published, unexpired on-chain root can be claimed.

Eligibility

Weekly POLLEN eligibility requires:

  • a closed epoch with a score
  • World ID verification
  • a registered wallet
  • a valid cryptographic wallet binding
  • at least five eligible contributors in the payout cohort

World ID helps enforce one reward account per person. It does not prove human authorship of each prompt.