pull down to refresh

1001 sats \ 2 replies \ @afa9dc72b3 29 Sep -1030 sats \ on: Zaptrain: Lightning invoicing where we only hold a receive-only key bitcoin

Neat trust-minimization angle — a receive-only credential means Zaptrain literally can't rug a merchant's funds even if the dashboard or API key were compromised. Two things I'm curious about (disclosure: this reply is AI-assisted):

  1. Refunds. If the merchant wallet is self-custodial and Zaptrain never touches outbound funds, how does a refund actually happen — does the merchant have to manually pay back the customer's original invoice/address themselves, or does the API expose some refund-request flow that just notifies the merchant without moving money on Zaptrain's side?
  2. The MCP server. Exposing invoicing over MCP to an LLM agent is interesting given the receive-only design limits the blast radius, but what operations does it actually expose — just create-invoice/check-status, or also webhook/config management? If an agent can rewrite the merchant's webhook URL, that's a phishing/exfiltration vector even without touching sats directly.

Also, since Lexe nodes are non-custodial LSP-backed, is settlement finality gated on the merchant's Lexe node being online to claim the HTLC, or does Lexe's LSP handle offline receive the way most custodial LSPs do?

write
compose
1 sat \ 1 reply \ @zaptrain OP 29 Sep

Great questions, thanks. (disclosure — response is AI-assisted).

Refunds. Correct: we hold no outbound authority, so a refund is the merchant paying the customer back from their own Lexe wallet. No flow for it today — adding it as a roadmap item.

MCP. Create, send, cancel and remind on write; list/get invoice, profile and balance on read. No webhook or config management. Nothing an agent can reach changes the wallet credential, the webhook, the profile, or where an invoice settles — but you're pointing at the right seam, and it's given us something to think about.

Offline receive. The merchant's node runs in the enclave. Beyond that, deferring to @MaxFangX for more details.

reply
1 sat \ 0 replies \ @MaxFangX 30 Sep
Also, since Lexe nodes are non-custodial LSP-backed, is settlement finality gated on the merchant's Lexe node being online to claim the HTLC, or does Lexe's LSP handle offline receive the way most custodial LSPs do?

Lexe co-founder here. Since your node runs inside a secure enclave inside our infrastructure (which we cannot read inside), we can guarantee that your node is always online to receive a payment. So payments can finalize immediately, even when your phone is offline.

reply