Merge pull request #3293 from halseth/bumpfee-doc

[trivial] lnrpc: make BumpFee doc start with RPC name
This commit is contained in:
Wilmer Paulino 2019-07-10 12:02:41 -07:00 committed by GitHub
commit 03cf9a53e4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 24 additions and 24 deletions

@ -903,14 +903,14 @@ type WalletKitClient interface {
//the UtxoSweeper, so things may change.
PendingSweeps(ctx context.Context, in *PendingSweepsRequest, opts ...grpc.CallOption) (*PendingSweepsResponse, error)
//
//Bump the fee of an arbitrary input within a transaction. This RPC takes a
//different approach than bitcoind's bumpfee command. lnd has a central
//batching engine in which inputs with similar fee rates are batched together
//to save on transaction fees. Due to this, we cannot rely on bumping the fee
//on a specific transaction, since transactions can change at any point with
//the addition of new inputs. The list of inputs that currently exist within
//lnd's central batching engine can be retrieved through the PendingSweeps
//RPC.
//BumpFee bumps the fee of an arbitrary input within a transaction. This RPC
//takes a different approach than bitcoind's bumpfee command. lnd has a
//central batching engine in which inputs with similar fee rates are batched
//together to save on transaction fees. Due to this, we cannot rely on
//bumping the fee on a specific transaction, since transactions can change at
//any point with the addition of new inputs. The list of inputs that
//currently exist within lnd's central batching engine can be retrieved
//through the PendingSweeps RPC.
//
//When bumping the fee of an input that currently exists within lnd's central
//batching engine, a higher fee transaction will be created that replaces the
@ -1052,14 +1052,14 @@ type WalletKitServer interface {
//the UtxoSweeper, so things may change.
PendingSweeps(context.Context, *PendingSweepsRequest) (*PendingSweepsResponse, error)
//
//Bump the fee of an arbitrary input within a transaction. This RPC takes a
//different approach than bitcoind's bumpfee command. lnd has a central
//batching engine in which inputs with similar fee rates are batched together
//to save on transaction fees. Due to this, we cannot rely on bumping the fee
//on a specific transaction, since transactions can change at any point with
//the addition of new inputs. The list of inputs that currently exist within
//lnd's central batching engine can be retrieved through the PendingSweeps
//RPC.
//BumpFee bumps the fee of an arbitrary input within a transaction. This RPC
//takes a different approach than bitcoind's bumpfee command. lnd has a
//central batching engine in which inputs with similar fee rates are batched
//together to save on transaction fees. Due to this, we cannot rely on
//bumping the fee on a specific transaction, since transactions can change at
//any point with the addition of new inputs. The list of inputs that
//currently exist within lnd's central batching engine can be retrieved
//through the PendingSweeps RPC.
//
//When bumping the fee of an input that currently exists within lnd's central
//batching engine, a higher fee transaction will be created that replaces the

@ -274,14 +274,14 @@ service WalletKit {
rpc PendingSweeps(PendingSweepsRequest) returns (PendingSweepsResponse);
/*
Bump the fee of an arbitrary input within a transaction. This RPC takes a
different approach than bitcoind's bumpfee command. lnd has a central
batching engine in which inputs with similar fee rates are batched together
to save on transaction fees. Due to this, we cannot rely on bumping the fee
on a specific transaction, since transactions can change at any point with
the addition of new inputs. The list of inputs that currently exist within
lnd's central batching engine can be retrieved through the PendingSweeps
RPC.
BumpFee bumps the fee of an arbitrary input within a transaction. This RPC
takes a different approach than bitcoind's bumpfee command. lnd has a
central batching engine in which inputs with similar fee rates are batched
together to save on transaction fees. Due to this, we cannot rely on
bumping the fee on a specific transaction, since transactions can change at
any point with the addition of new inputs. The list of inputs that
currently exist within lnd's central batching engine can be retrieved
through the PendingSweeps RPC.
When bumping the fee of an input that currently exists within lnd's central
batching engine, a higher fee transaction will be created that replaces the