Archives/loop
2
0
Fork 0
mirror of https://github.com/lightninglabs/loop synced 2024-11-04 06:00:21 +00:00
Code Issues Releases Wiki Activity

Merge pull request #254 from gcomte/master

Browse Source 
looprpc/docs: fix typo
This commit is contained in:
Oliver Gugger 2020-07-17 16:21:28 +02:00 committed by GitHub
commit 9efca9da11
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
looprpc/client.pb.go
View File

@ -138,7 +138,7 @@ type LoopOutRequest struct {
//Maximum amount of the swap fee that may be charged as a prepayment.
MaxPrepayAmt int64 `protobuf:"varint,6,opt,name=max_prepay_amt,json=maxPrepayAmt,proto3" json:"max_prepay_amt,omitempty"`
//*
//Maximum in on-chain fees that we are willing to spent. If we want to
//Maximum in on-chain fees that we are willing to spend. If we want to
//sweep the on-chain htlc and the fee estimate turns out higher than this
//value, we cancel the swap. If the fee estimate is lower, we publish the
//sweep tx.
@ -294,7 +294,7 @@ type LoopInRequest struct {
//response of the GetQuote call.
MaxSwapFee int64 `protobuf:"varint,2,opt,name=max_swap_fee,json=maxSwapFee,proto3" json:"max_swap_fee,omitempty"`
//*
//Maximum in on-chain fees that we are willing to spent. If we want to
//Maximum in on-chain fees that we are willing to spend. If we want to
//publish the on-chain htlc and the fee estimate turns out higher than this
//value, we cancel the swap.
//

4
looprpc/client.proto
View File

@ -145,7 +145,7 @@ message LoopOutRequest {
int64 max_prepay_amt = 6;
/**
Maximum in on-chain fees that we are willing to spent. If we want to
Maximum in on-chain fees that we are willing to spend. If we want to
sweep the on-chain htlc and the fee estimate turns out higher than this
value, we cancel the swap. If the fee estimate is lower, we publish the
sweep tx.
@ -208,7 +208,7 @@ message LoopInRequest {
int64 max_swap_fee = 2;
/**
Maximum in on-chain fees that we are willing to spent. If we want to
Maximum in on-chain fees that we are willing to spend. If we want to
publish the on-chain htlc and the fee estimate turns out higher than this
value, we cancel the swap.

4
looprpc/client.swagger.json
View File

@ -381,7 +381,7 @@
"max_miner_fee": {
"type": "string",
"format": "int64",
"description": "*\nMaximum in on-chain fees that we are willing to spent. If we want to\npublish the on-chain htlc and the fee estimate turns out higher than this\nvalue, we cancel the swap. \n\nmax_miner_fee is typically taken from the response of the GetQuote call."
"description": "*\nMaximum in on-chain fees that we are willing to spend. If we want to\npublish the on-chain htlc and the fee estimate turns out higher than this\nvalue, we cancel the swap. \n\nmax_miner_fee is typically taken from the response of the GetQuote call."
},
"last_hop": {
"type": "string",
@ -435,7 +435,7 @@
"max_miner_fee": {
"type": "string",
"format": "int64",
"description": "*\nMaximum in on-chain fees that we are willing to spent. If we want to\nsweep the on-chain htlc and the fee estimate turns out higher than this\nvalue, we cancel the swap. If the fee estimate is lower, we publish the\nsweep tx.\n\nIf the sweep tx is not confirmed, we are forced to ratchet up fees until it\nis swept. Possibly even exceeding max_miner_fee if we get close to the htlc\ntimeout. Because the initial publication revealed the preimage, we have no\nother choice. The server may already have pulled the off-chain htlc. Only\nwhen the fee becomes higher than the swap amount, we can only wait for fees\nto come down and hope - if we are past the timeout - that the server is not\npublishing the revocation.\n\nmax_miner_fee is typically taken from the response of the GetQuote call."
"description": "*\nMaximum in on-chain fees that we are willing to spend. If we want to\nsweep the on-chain htlc and the fee estimate turns out higher than this\nvalue, we cancel the swap. If the fee estimate is lower, we publish the\nsweep tx.\n\nIf the sweep tx is not confirmed, we are forced to ratchet up fees until it\nis swept. Possibly even exceeding max_miner_fee if we get close to the htlc\ntimeout. Because the initial publication revealed the preimage, we have no\nother choice. The server may already have pulled the off-chain htlc. Only\nwhen the fee becomes higher than the swap amount, we can only wait for fees\nto come down and hope - if we are past the timeout - that the server is not\npublishing the revocation.\n\nmax_miner_fee is typically taken from the response of the GetQuote call."
},
"loop_out_channel": {
"type": "string",