Send Transaction

Use this skill to transfer assets. It handles both native ETH and ERC-20 tokens.

Hard Rules (CRITICAL)

Pre-Flight Check: Before ANY send operation, you MUST run:
- ```
npx fibx@latest status
```
  (to ensure connectivity)
- ```
npx fibx@latest balance
```
  (to ensure sufficient funds)
Recipient Confirmation: If the user provides a recipient address that has NOT been mentioned in the current conversation history, you MUST ask for explicit confirmation before sending.
- Agent: "I am about to send 10 USDC to 0x123...456. Is this correct?"
Chain Specification:
- If the user mentions a specific chain (e.g., "on Monad", "for my Citrea wallet"), you MUST include the
```
--chain <name>
```
  parameter.
- If the user DOES NOT mention a chain, you MUST either:
  - Explicitly state the default: "I will use Base for this transaction. Is that correct?"
  - OR ask for clarification: "Which chain would you like to use? Base, Citrea, HyperEVM, or Monad?"
Post-Flight Verification: After the CLI returns a transaction hash, you MUST use the
```
tx-status
```
skill to verify it was included in a block and provide the explorer link to the user.

bash

npx fibx@latest send <amount> <recipient> [token] [--chain <chain>] [--json]

Argument	Description
`amount`	Amount to send. Use simple numbers (e.g., `0.1` , `10` ). Avoid `$` symbols in the command itself.
`recipient`	The destination Ethereum address ( `0x...` ).
`token`	Optional. Token symbol ( `ETH` , `USDC` , `WETH` ). Defaults to `ETH` .

Option	Description
`--chain <network>`	Network to use: `base` , `citrea` , `hyperevm` , `monad` . Default: `base` .
`--json`	Output result as JSON.

User: "Send 10 USDC to 0x123...abc"

Agent Actions:

npx fibx@latest send 10 0x123...abc USDC

npx fibx@latest tx-status <hash_from_output>

User: "Send 0.05 MON to 0xdef...456 on Monad"

Agent Actions:

npx fibx@latest send 0.05 0xdef...456 ETH --chain monad

(Native token is treated as 'ETH' generic or 'MON')

npx fibx@latest tx-status <hash> --chain monad