Skip to content

Plumb an optional fee_claim through register_node#26

Merged
amackillop merged 1 commit into
lsp-0.2.0from
austin_mdk-981_pass-fee-claim
Jun 11, 2026
Merged

Plumb an optional fee_claim through register_node#26
amackillop merged 1 commit into
lsp-0.2.0from
austin_mdk-981_pass-fee-claim

Conversation

@amackillop

Copy link
Copy Markdown

MDK-980 added the fee_claim field to RegisterNodeRequest and the verifier that reads it, but the client still hardcoded None, so no node could ever present a claim. This lets the caller pass one.

The claim rides as a per-call argument rather than a field on LSPS4ClientConfig: that config derives Copy, which an Option would break, and the value belongs to the layer above (ldk-node), which already holds it and relays it on every registration. There is a single call site, so threading it as a parameter is the smaller, honest change.

The value is opaque here: a lowercase-hex signed grant the LSP alone decodes and verifies. Passing None reproduces today's behavior exactly, so nothing changes until a node is configured with a claim.

MDK-980 added the fee_claim field to RegisterNodeRequest and the verifier
that reads it, but the client still hardcoded None, so no node could ever
present a claim. This lets the caller pass one.

The claim rides as a per-call argument rather than a field on
LSPS4ClientConfig: that config derives Copy, which an Option<String> would
break, and the value belongs to the layer above (ldk-node), which already
holds it and relays it on every registration. There is a single call site,
so threading it as a parameter is the smaller, honest change.

The value is opaque here: a lowercase-hex signed grant the LSP alone decodes
and verifies. Passing None reproduces today's behavior exactly, so nothing
changes until a node is configured with a claim.
@amackillop amackillop merged commit 3e0a0f0 into lsp-0.2.0 Jun 11, 2026
10 of 43 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant