archon-cashu_skill

Overview

This skill integrates Cashu ecash operations with an Archon DID to create P2PK-locked tokens and manage ecash wallets. It enables sending sats that only a DID-derived public key can unlock and supports wallet backup to a vault. The skill also includes Lightning minting, optional LNBITS integration, and npub.cash setup for Nostr zaps.

How this skill works

The skill uses your Archon identity and local Cashu CLI to create, lock, and redeem tokens. DID-locked tokens are created by deriving a secp256k1 public key from the recipient's Archon DID and using P2PK locking so only the DID owner can unlock them. Scripts handle balance checks, sending (locked or unlocked), receiving, minting via Lightning, and wallet backups to a vault DID.

When to use it

• Send sats that only a specific Archon DID can spend (DID-locked payments).
• Operate a local Cashu ecash wallet with simple scripts for common flows.
• Mint tokens via Lightning and optionally auto-pay using LNBITS.
• Backup wallet state to a vault DID for recovery and custody.
• Integrate Nostr zap flows with npub.cash for tipping and zaps.

Best practices

• Store your Archon identity config securely (e.g., ~/.archon.env) and never expose private keys.
• Verify recipient DID and derived pubkey before creating DID-locked tokens.
• Keep wallet directory backups and test recovery from the vault periodically.
• Use LNBITS integration only with trusted instances to avoid automated payment risks.
• Run scripts in a secure environment and set CASHU_WALLET_DIR explicitly if not using the default.

Example use cases

• Send 100 sats locked to a collaborator's Archon DID; only they can redeem.
• Mint 500 sats by creating a Lightning invoice and receive tokens in the Cashu wallet.
• Backup your local Cashu wallet to a vault DID before migrating machines.
• Configure npub.cash to allow Nostr zaps to mint or route ecash payments.
• Check balance and reconcile tokens before initiating locked transfers.