● 社区
aelf-hzz780
⚡ 即开即用
AI-bounty-skill
作者 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.
为什么要用
核心特性
- 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
实时演示
实际使用效果
ai-bounty-skill.replay
▶ 就绪
使用场景
实战用法: AI-bounty-skill
何时使用: You were rewarded in the aelf AI bounty program and want Claude to walk the RewardClaimContract Claim() call instead of hand-rolling it.
步骤
-
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.✓ 已复制
→ 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.✓ 已复制
→ Payload ready, you broadcast, claim lands
结果: Bounty claimed with a transaction hash you control, no custodial middleman.
注意事项
- Using an exchange deposit address as target — Use a self-custody address — exchanges don't route the reward metadata correctly
何时使用: Your aelf identity is a Portkey CA, not a raw EOA.
前置条件
- Portkey account recovery / login prepared — Use your registered email to recover/login at portkey.finance
步骤
-
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.✓ 已复制
→ 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.✓ 已复制
→ Portkey prompts, you approve, tx confirmed
结果: Bounty lands in your Portkey-managed CA address.
注意事项
- Mixing EOA and CA code paths — Pick the one that matches how the bounty was assigned — the skill has separate flows for a reason
组合
与其他 MCP 搭配,撬动十倍杠杆
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.✓ 已复制
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.✓ 已复制
成本与限制
运行它的成本
- API 配额
- None — skill is prompts only
- 每次调用 Token 数
- <2k
- 费用
- Free skill. You pay aelf tDVV gas on broadcast.
- 提示
- Batch any other pending actions into the same session to amortize context setup.
安全
权限、密钥、影响范围
凭据存储: No credentials inside the skill. Private keys stay in your local aelf tool or Portkey.
数据出站: None by the skill itself. Broadcasting hits aelf tDVV RPC.
切勿授予: 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.
故障排查
常见错误与修复
Claim() reverts with 'not eligible'
Confirm the bounty is assigned to the exact address you're calling from, on tDVV (not mainchain).
验证: 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.
验证: Check balance via aelf CLI: aelf-command call -a <address> AElf.ContractNames.Token GetBalance
替代方案
AI-bounty-skill 对比其他方案
| 替代方案 | 何时用它替代 | 权衡 |
| Direct aelf CLI | You're comfortable hand-writing the contract call | No guidance, but no skill dependency either |