菜单
Maintained eCash AI-agent skill for Claude Code, Codex, Cursor, OpenCode, and compatible coding agents
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | ecash |
| description | Maintained eCash AI-agent skill for Claude Code, Codex, Cursor, OpenCode, and compatible coding agents |
| version | 0.4.1 |
| tags | ["ecash","blockchain","bitcoin-abc","chronik","wallet","tokens","xec"] |
Run this at the start of every session to check for updates:
_SKILL_DIR=$(find ~/.claude/plugins ~/.claude/skills ~/.agents/skills -name 'ecashskill' -maxdepth 3 -type d 2>/dev/null | head -1)
_LOCAL_VER=$(cat "$_SKILL_DIR/VERSION" 2>/dev/null || echo "unknown")
_REMOTE_VER=$(curl -sf --max-time 3 https://raw.githubusercontent.com/alitayin/ecashskill/main/VERSION 2>/dev/null | tr -d '[:space:]' || echo "")
[ -n "$_REMOTE_VER" ] && [ "$_REMOTE_VER" != "$_LOCAL_VER" ] && echo "UPGRADE_AVAILABLE $_LOCAL_VER $_REMOTE_VER" || true
If output shows UPGRADE_AVAILABLE <old> <new>:
Tell the user: "ecashskill v{new} is available (you're on v{old}). Update with:
claude plugin install alitayin/ecashskill
```"
# eCash AI Skill
eCash AI Skill is a maintained skill package for AI coding agents working on
eCash apps. It gives Claude Code, Codex, Cursor, OpenCode, and compatible agents
concise project context, library selection guidance, coding rules, and testing
patterns for Chronik, ecash-lib, wallets, tokens, Agora, Cashtab, and PayButton.
## Scope
Use this skill as the eCash knowledge and workflow layer inside an AI coding
agent. It helps the agent choose the right eCash library, handle XEC and token
units correctly, avoid key-handling mistakes, and write tests that do not depend
on public Chronik availability.
## What is eCash?
eCash (XEC) is a cryptocurrency that forked from Bitcoin Cash in 2021, built on Bitcoin ABC node technology. It uses the Avalanche consensus mechanism for fast transaction finality and supports both SLP and ALP token standards.
**Key Facts:**
- **Token**: XEC (1 XEC = 100 satoshis)
- **Address Format**: CashAddr with `ecash:` prefix
- **BIP44 Coin Type**: Varies by wallet - ecash-wallet uses 1899, Electrum ABC uses 899
- **Node Implementation**: Bitcoin ABC
- **Consensus**: Avalanche (fast finality)
- **Website**: https://e.cash
## References Overview
The `references/` folder contains documentation for different tools and libraries:
| Reference | Purpose | When to Use |
|-----------|---------|-------------|
| `chronik/` | Blockchain indexer API | Querying blockchain data, WebSocket subscriptions |
| `chronik-client.md` | Client library for Chronik | Most development work involving blockchain queries |
| `ecash-lib.md` | Transaction building & signing | Creating raw transactions, custom signing logic |
| `ecash-wallet.md` | HD wallet implementation | Managing wallets, sending XEC/tokens |
| `ecashaddrjs.md` | Address encoding/decoding | Address validation, format conversion |
| `ecash-agora.md` | Decentralized exchange protocol | Building marketplaces, token trading |
| `ecash-quicksend.md` | Quick transaction sending | Simple payments, prototypes, small projects |
| `cashtab.md` | Web wallet reference | Reference implementation, wallet UI patterns |
| `cashtab-connect.md` | Browser extension integration | DApp wallet connection |
| `paybutton.md` | Embeddable payment button | Accepting eCash on websites, donations, e-commerce |
| `bitcoin-abc.md` | Node implementation | Contributing to Bitcoin ABC, understanding internals |
| `mock-chronik-client.md` | Testing utilities | Writing unit tests |
| `examples.md` | Code examples | Quick reference for common patterns |
## Library Selection
Use this decision table before writing code:
| Task | Recommended tool | Notes |
|------|------------------|-------|
| Query chain state | `chronik-client` | Prefer explicit Chronik endpoint arrays and retry around network boundaries |
| Build custom transactions | `ecash-lib` | Keep amounts as `bigint` satoshis and test serialization with fixtures |
| Manage mnemonic wallets | `ecash-wallet` | Use BIP44 coin type `1899` unless matching another wallet's existing path |
| Add a simple payment button | `@paybutton/react` or `@paybutton/paybutton` | Best for website checkout, donations, and hosted UI flows |
| Send XEC/tokens in scripts | `ecash-quicksend` | Useful for prototypes and internal scripts; avoid for critical wallet products |
| Integrate a browser wallet | `cashtab-connect` | Handle user denial, unavailable extension, and timeout errors explicitly |
| Trade tokens | `ecash-agora` | Understand atom units and covenant signing before accepting or listing offers |
## Coding Rules
- Treat XEC amounts carefully: `1 XEC = 100 satoshis`; library APIs often expect satoshis or token atoms, not decimal XEC.
- Prefer `bigint` for satoshis and token atoms. Convert display strings at UI boundaries only.
- Validate eCash addresses with `ecashaddrjs` before sending funds.
- Never log mnemonics, private keys, raw seed material, or signed transactions containing sensitive metadata.
- Use `chronik-client` or a mocked Chronik client in tests. Do not make unit tests depend on public Chronik availability.
- When using WebSockets, include reconnect handling and unsubscribe/close during cleanup.
- For tokens, identify both protocol (`SLP` or `ALP`) and token type before constructing sends or offers.
## When to Use
Use this skill when:
- Building applications on eCash blockchain
- Integrating with Chronik indexer
- Creating or managing eCash wallets
- Working with SLP/ALP Tokens
- Developing payment solutions
- Adding a PayButton payment widget to a website
- Analyzing blockchain data
## Tools & Libraries
### Infrastructure
- **chronik** - High-performance blockchain indexer (see `references/chronik/chronik.md`)
- **chronik-client** - Client library for Chronik (see `references/chronik-client.md`)
- **bitcoin-abc** - Node implementation (see `references/bitcoin-abc.md`)
### Transaction & Signing
- **ecash-lib** - Transaction building and signing (see `references/ecash-lib.md`)
- **ecash-quicksend** - Simple transaction sender for quick payments (see `references/ecash-quicksend.md`)
### Wallet
- **ecash-wallet** - HD wallet with XEC and token support (see `references/ecash-wallet.md`)
### Utilities
- **ecashaddrjs** - Address encoding/decoding (see `references/ecashaddrjs.md`)
### Applications
- **cashtab** - Web wallet reference (see `references/cashtab.md`)
- **cashtab-connect** - Browser extension integration (see `references/cashtab-connect.md`)
- **ecash-agora** - Marketplace application (see `references/ecash-agora.md`)
- **paybutton** - Embeddable payment button for websites (see `references/paybutton.md`)
### Testing
- **mock-chronik-client** - Mock for testing (see `references/mock-chronik-client.md`)
## Testing Strategy
- Use `mock-chronik-client` for address, token, UTXO, and transaction scenarios.
- Store transaction fixtures as hex strings with expected txids and decoded outputs.
- Test dust, insufficient funds, invalid address, token mismatch, and Chronik error branches.
- Keep integration tests opt-in when they touch public Chronik endpoints.
- For UI apps, cover wallet-denied, extension-missing, pending-payment, and payment-success states.
## Quick Start
```typescript
import { ChronikClient } from 'chronik-client';
const chronik = new ChronikClient(['https://chronik.e.cash/']);
For more available Chronik nodes, see https://chronik.cash.
All tool documentation is available in the references/ folder.