Skip to content

Latest commit

 

History

History
50 lines (36 loc) · 1.67 KB

File metadata and controls

50 lines (36 loc) · 1.67 KB

nwc for Hermes — installed ✓

Your Hermes Agent now has 5 tools in the nwc toolset:

  • nwc_get_info — wallet capabilities
  • nwc_balance — current balance
  • nwc_pay_invoice — pay BOLT11 invoice ⚠ spends funds
  • nwc_make_invoice — create BOLT11 invoice
  • nwc_list_transactions — recent tx history

One-time setup

This plugin needs NWC_URI in the environment — a connection string from your wallet service. Get one from:

  • Alby — Settings → Wallet Connections → New Connection
  • Mutiny — Settings → Connections → Add Application
  • LNbits — Extensions → NWC Service Provider → New Connection
  • Self-hosted — any NIP-47-capable wallet daemon

Set it:

export NWC_URI="nostr+walletconnect://<pubkey>?relay=wss://...&secret=..."

Add to your shell rc, or to $HERMES_HOME/.env if Hermes loads from there. Use a dedicated agent wallet with a small balance. Set a per-connection spend cap at the wallet — most NWC implementations support daily budgets.

After setting the env var, restart Hermes (the plugin reads it once at dispatch time per call).

First run

> Check the wallet balance.

Should call nwc_balance and return {"balance_msats": ..., "balance_sats": ...}. If you see NWC_URI env var is not set, the env wasn't passed into the Hermes process — make sure your shell rc loaded it before launch.

Source