Claude Code skill that walks you through claiming the aelf AI bounty on tDVV via RewardClaimContract — supports both EOA and Portkey CA wallets.
A narrow-purpose skill: given you already have an aelf AA/CA wallet set up (non-custodial, not an exchange address), it guides Claude through calling Claim() or ClaimByPortkeyToCa() correctly on the RewardClaimContract. It does not hold keys itself — signing stays in Portkey. Treat it as instructional glue, not a wallet.
👤 aelf developers holding the bounty in a self-custody EOA⏱ ~15 minintermediate
Wann einsetzen: You were rewarded in the aelf AI bounty program and want Claude to walk the RewardClaimContract Claim() call instead of hand-rolling it.
Ablauf
Load your wallet context locally and ask the skill to lay out the call
Use the AI-bounty-skill to prepare a Claim() transaction on RewardClaimContract for my EOA. Show me the args and the signing preview before broadcast.✓ Kopiert
→ Claude enumerates contract address, method, and args — pauses for confirmation
Sign and broadcast via your own tool
Looks good — give me the signed tx payload to send via my local aelf CLI.✓ Kopiert
→ Payload ready, you broadcast, claim lands
Ergebnis: Bounty claimed with a transaction hash you control, no custodial middleman.
Fallstricke
Using an exchange deposit address as target — Use a self-custody address — exchanges don't route the reward metadata correctly
Claim the bounty through a Portkey CA (account abstraction) wallet
👤 Users whose bounty is tied to a Portkey-managed social login⏱ ~15 minintermediate
Wann einsetzen: Your aelf identity is a Portkey CA, not a raw EOA.
Voraussetzungen
Portkey account recovery / login prepared — Use your registered email to recover/login at portkey.finance
Ablauf
Ask Claude to assemble a ClaimByPortkeyToCa() call
Use AI-bounty-skill to prepare ClaimByPortkeyToCa() — my CA hash is <hash>. Show me what will be signed by Portkey.✓ Kopiert
→ Claude outputs the exact method and args, and tells you Portkey will prompt for signature
Approve in Portkey
Send it — I'll approve in Portkey.✓ Kopiert
→ Portkey prompts, you approve, tx confirmed
Ergebnis: Bounty lands in your Portkey-managed CA address.
Fallstricke
Mixing EOA and CA code paths — Pick the one that matches how the bounty was assigned — the skill has separate flows for a reason