kaspa-wallet

What This Skill Does

The Kaspa Wallet skill provides a robust, self-custody interface for interacting with the Kaspa blockchain directly from your terminal. It enables seamless management of KAS assets by acting as a bridge between the OpenClaw agent and the Kaspa wRPC network. Unlike custodial services, this skill prioritizes security through local mnemonic management, allowing users to check balances, initiate transactions, and generate standard payment URIs without exposing private keys to third-party servers. It is architected for automation, returning structured JSON output that can be piped into other system processes.

Installation

To integrate this skill, use the ClawHub command: clawhub install openclaw/skills/skills/manyfestation/kaspa. Ensure you have Python 3.8+ installed on your system. The provided install.py script automatically configures a virtual environment to manage dependencies, ensuring your system path remains clean. If you encounter issues, verify that your environment has venv support; on Debian/Ubuntu systems, you may need to run sudo apt install python3-venv before execution.

Use Cases

This skill is ideal for developers and power users who require programmatic access to Kaspa. Use it for: 1. Automating recurring payments or merchant transaction verification. 2. Integrating Kaspa payments into local workflows or CLI-based dashboards. 3. Monitoring wallet balances and network health through automated polling scripts. 4. Quickly generating payment requests for point-of-sale or digital invoice scenarios.

Example Prompts

1. "Check the current balance for my wallet and tell me if the network is currently synced."
2. "Send 50 KAS to this address: kaspa:qrc8y... and let me know the transaction ID."
3. "Generate a payment URI for 12.5 KAS with the memo 'Freelance Invoice' and save it to my clipboard."

Tips & Limitations

Always store your generated mnemonic in a secure, offline location; the skill relies on local custody, meaning lost mnemonics equal permanent loss of funds. Be aware that the send command requires active node connectivity. If you face transaction submission errors, check the info command to ensure the node is fully synced. For high-volume usage, consider pointing the skill to a dedicated, high-availability wRPC node endpoint.