# EOA Claim

Use this branch for the EOA claim path after account type selection is complete.

## Required Dependency

Use the Portkey EOA skill explicitly:

- `https://github.com/Portkey-Wallet/eoa-agent-skills`

## When To Use

Use this flow only when all conditions below are true:

- the user explicitly chose `EOA`
- a local EOA account is already available
- no AA/CA identity flow is involved
- account choice is already complete

## Required Facts

- Method: `Claim()`
- Receiver: `Context.Sender`
- Current campaign default reward: `1 AIBOUNTY`
- `ca_hash` is not part of this flow
- EOA must have enough `ELF` to pay transaction gas before sending `Claim()`
- If the user cannot get enough `ELF`, the recommended fallback is to switch to `AA/CA`

## Step-By-Step

1. Tell the user not to fill exchange or custodial addresses.
2. Validate the `tDVV` RPC through `https://tdvv-public-node.aelf.io/api/blockChain/chainStatus`.
3. Use the Portkey EOA skill dependency to resolve the active signer from the local EOA account context.
4. If the resolved address is exchange-managed, custodial, or signer ownership is unclear, stop and switch to [diagnostics-stop.md](./diagnostics-stop.md).
5. Check that the claim contract is currently claimable on `tDVV` through verified read methods from the validated ABI, contract source, or dependency skill; do not guess method names.
6. Check that the resolved local EOA address has not already claimed through verified read methods from the validated ABI, contract source, or dependency skill; do not guess method names.
7. Check that the resolved local EOA address has enough `ELF` to pay transaction gas.
8. If the local EOA does not have enough `ELF`, stop and switch to [diagnostics-stop.md](./diagnostics-stop.md).
9. In that stop response, tell the user to transfer in enough `ELF` before retrying, and also tell them to switch to `AA/CA` if getting `ELF` is not feasible.
10. Show the write summary:
   - signer address
   - contract address
   - method `Claim()`
   - receiver semantics `reward goes to Context.Sender`
   - source of signer `resolved from local EOA account`
   - expected reward `1 AIBOUNTY` in the current campaign
   - RPC validation endpoint `https://tdvv-public-node.aelf.io/api/blockChain/chainStatus`
   - gas prerequisite `EOA has enough ELF to pay gas`
11. Ask for explicit confirmation.
12. Only after explicit confirmation, send `Claim()`.
13. If a `txId` is returned immediately, share the `txId` and `https://aelfscan.io/tDVV/tx/<txid>` while continuing to poll for the final result.
14. If the first query result is `NOTEXISTED`, wait briefly and query the transaction again; do not treat `NOTEXISTED` as a final result.
15. Report the `txId`, the exact final chain result, and `https://aelfscan.io/tDVV/tx/<txid>`.
16. If the final transaction error is `Transaction fee not enough`, map it to insufficient transaction fee, tell the user to add `ELF`, and recommend switching to `AA/CA` if `ELF` cannot be obtained.
17. If the transaction fails for another reason, surface the original error and stop.

## Must-Stop Conditions

Stop immediately if any of the following is true:

- the address belongs to OKX or another exchange
- the contract is not claimable yet
- the address has already claimed
- the user asks for `ca_hash` handling in this branch
- no local EOA account can be resolved
- `/api/blockChain/chainStatus` cannot be reached
- the local EOA does not have enough `ELF` to pay gas

## Output Shape

The response before sending the transaction should contain:

- chosen flow: `EOA Claim`
- resolved signer
- target contract
- method
- receiver semantics
- signer source `local EOA account`
- reward amount
- gas prerequisite status
- explicit confirmation request
- when gas is insufficient, a stop response that includes both `add ELF` and `switch to AA/CA if ELF is unavailable`

## Example Reference

Read [../examples/eoa-skill.md](../examples/eoa-skill.md) before replying.