● Communauté
aelf-hzz780
⚡ Instantané
AI-bounty-skill
par aelf-hzz780 · aelf-hzz780/AI-bounty-skill
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.
Pourquoi l'utiliser
Fonctionnalités clés
- Step-by-step flow for both EOA and Portkey CA claim paths
- Defers all signing to Portkey — no private key or seed phrase handling
- Explicit warning against using exchange/custodial addresses
- Works on aelf tDVV sidechain only
Démo en direct
Aperçu en pratique
ai-bounty-skill.replay
▶ prêt
Cas d'usage
Usages concrets : AI-bounty-skill
Quand l'utiliser : You were rewarded in the aelf AI bounty program and want Claude to walk the RewardClaimContract Claim() call instead of hand-rolling it.
Déroulement
-
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.✓ Copié
→ 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.✓ Copié
→ Payload ready, you broadcast, claim lands
Résultat : Bounty claimed with a transaction hash you control, no custodial middleman.
Pièges
- Using an exchange deposit address as target — Use a self-custody address — exchanges don't route the reward metadata correctly
Quand l'utiliser : Your aelf identity is a Portkey CA, not a raw EOA.
Prérequis
- Portkey account recovery / login prepared — Use your registered email to recover/login at portkey.finance
Déroulement
-
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.✓ Copié
→ 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.✓ Copié
→ Portkey prompts, you approve, tx confirmed
Résultat : Bounty lands in your Portkey-managed CA address.
Pièges
- Mixing EOA and CA code paths — Pick the one that matches how the bounty was assigned — the skill has separate flows for a reason
Combinaisons
Associez-le à d'autres MCPs pour un effet X10
Use aelf-skills to bootstrap your dev environment and verify wallet, then AI-bounty-skill to claim
Run aelf-skills health to confirm my wallet and node are working, then use AI-bounty-skill to prepare my bounty claim.✓ Copié
Read your local wallet config to confirm the correct address before claiming
Read my aelf wallet config at ~/.aelf/keys/, confirm the address, then use AI-bounty-skill to prepare the Claim() call for that address.✓ Copié
Coût et limites
Coût d'exécution
- Quota d'API
- None — skill is prompts only
- Tokens par appel
- <2k
- Monétaire
- Free skill. You pay aelf tDVV gas on broadcast.
- Astuce
- Batch any other pending actions into the same session to amortize context setup.
Sécurité
Permissions, secrets, portée
Stockage des identifiants : No credentials inside the skill. Private keys stay in your local aelf tool or Portkey.
Sortie de données : None by the skill itself. Broadcasting hits aelf tDVV RPC.
Ne jamais accorder : Paste your seed phrase into the chat — the skill never asks for it
- Crypto domain — verify the contract address in the skill matches the official aelf bounty contract before signing anything.
- Do not use an exchange deposit address as the claim target.
- This skill is community-authored with modest stars; read SKILL.md end-to-end before use.
Dépannage
Erreurs courantes et correctifs
Claim() reverts with 'not eligible'
Confirm the bounty is assigned to the exact address you're calling from, on tDVV (not mainchain).
Vérifier : Check RewardClaimContract view methods for your address
Portkey prompt never appears
Make sure you're logged into Portkey in the same browser session as the tool that relays the tx.
Transaction fails with insufficient gas
Fund your tDVV address with ELF tokens for gas. Use the aelf faucet for testnet or transfer from mainchain via cross-chain bridge.
Vérifier : Check balance via aelf CLI: aelf-command call -a <address> AElf.ContractNames.Token GetBalance
Alternatives
AI-bounty-skill vs autres
| Alternative | Quand l'utiliser | Compromis |
|---|
| Direct aelf CLI | You're comfortable hand-writing the contract call | No guidance, but no skill dependency either |