Signet and regtest support for L402 and manual capture #8

Closed
opened 2026-10-09 11:20:33 +00:00 by thesimplekid · 0 comments
Owner

Summary

Network has only Bitcoin and Testnet, so LDK Server on regtest or signet cannot be used. That rules out the simplest end-to-end setup: bitcoind regtest plus two LDK Server nodes, as in LDK Server's own e2e-tests.

Suggestion

Add Signet and Regtest. Keep x402 limited to the networks its lnbtc identifiers define (mainnet and testnet3): reject x402 or Both on the other networks at create_intent, and allow L402 and manual capture there. Add an end-to-end test on LDK Server's e2e-tests harness, covering:

  • two intents for one resource;
  • the first payment authorized and claimed;
  • the second rejected and failed back without revealing the preimage;
  • a payment made while the engine is closed being decided after reopening (#5).
## Summary `Network` has only `Bitcoin` and `Testnet`, so LDK Server on regtest or signet cannot be used. That rules out the simplest end-to-end setup: bitcoind regtest plus two LDK Server nodes, as in LDK Server's own `e2e-tests`. ## Suggestion Add `Signet` and `Regtest`. Keep x402 limited to the networks its `lnbtc` identifiers define (mainnet and testnet3): reject `x402` or `Both` on the other networks at `create_intent`, and allow L402 and manual capture there. Add an end-to-end test on LDK Server's `e2e-tests` harness, covering: - two intents for one resource; - the first payment authorized and claimed; - the second rejected and failed back without revealing the preimage; - a payment made while the engine is closed being decided after reopening (#5).
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
thesimplekid/satsettle#8
No description provided.