highperfocused/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2026-01-20 15:19:07 +01:00
Code Issues Packages Projects Releases Wiki Activity

rpc, doc: clarify the response of listtransactions RPC

Browse Source 
I noticed this behaviour while perf testing PR 27286 and it was not something
that I expected, updating the doc to make it present in the RPCHelp command.
This commit is contained in:
rkrux
2025-06-12 20:19:04 +05:30
parent 5757de4ddd
commit 1ed8e76165
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/wallet/rpc/transactions.cpp
View File

@@ -444,7 +444,11 @@ RPCHelpMan listtransactions()
return RPCHelpMan{
"listtransactions",
"If a label name is provided, this will return only incoming transactions paying to addresses with the specified label.\n"
"\nReturns up to 'count' most recent transactions skipping the first 'from' transactions.\n",
"Returns up to 'count' most recent transactions ordered from oldest to newest while skipping the first number of \n"
"transactions specified in the 'skip' argument. A transaction can have multiple entries in this RPC response. \n"
"For instance, a wallet transaction that pays three addresses — one wallet-owned and two external — will produce \n"
"four entries. The payment to the wallet-owned address appears both as a send entry and as a receive entry. \n"
"As a result, the RPC response will contain one entry in the receive category and three entries in the send category.\n",
{
{"label", RPCArg::Type::STR, RPCArg::Optional::OMITTED, "If set, should be a valid label name to return only incoming transactions\n"
"with the specified label, or \"*\" to disable filtering and return all transactions."},