Skip to content

Commit

Permalink
taprpc: add scid parameter to tchrpc.SendPayment
Browse files Browse the repository at this point in the history
  • Loading branch information
GeorgeTsagk committed Dec 3, 2024
1 parent 093860e commit 24b46d2
Show file tree
Hide file tree
Showing 3 changed files with 92 additions and 70 deletions.
152 changes: 82 additions & 70 deletions taprpc/tapchannelrpc/tapchannel.pb.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

5 changes: 5 additions & 0 deletions taprpc/tapchannelrpc/tapchannel.proto
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,11 @@ message SendPaymentRequest {
// contain a valid keysend record (key 5482373484 and a 32-byte preimage
// that corresponds to the payment hash).
routerrpc.SendPaymentRequest payment_request = 4;

// The rfq id to use for this payment. If the user sets this value then the
// payment will immediately be dispatched, skipping the rfq negotiation
// phase, and using the following rfq id instead.
bytes rfq_id = 5;
}

message SendPaymentResponse {
Expand Down
5 changes: 5 additions & 0 deletions taprpc/tapchannelrpc/tapchannel.swagger.json
Original file line number Diff line number Diff line change
Expand Up @@ -1455,6 +1455,11 @@
"payment_request": {
"$ref": "#/definitions/routerrpcSendPaymentRequest",
"description": "The full lnd payment request to send. All fields behave the same way as\nthey do for lnd's routerrpc.SendPaymentV2 RPC method (see the API docs\nat https://lightning.engineering/api-docs/api/lnd/router/send-payment-v2\nfor more details).\nTo send a keysend payment, the payment_request.dest_custom_records must\ncontain a valid keysend record (key 5482373484 and a 32-byte preimage\nthat corresponds to the payment hash)."
},
"rfq_id": {
"type": "string",
"format": "byte",
"description": "The rfq id to use for this payment. If the user sets this value then the\npayment will immediately be dispatched, skipping the rfq negotiation\nphase, and using the following rfq id instead."
}
}
},
Expand Down

0 comments on commit 24b46d2

Please sign in to comment.