REST equivalent for gettxspendingprevout #33808

1. 
   valentinewallace commented at 9:38 pm on November 6, 2025: none

   This becomes more useful with #24539.

   This would be useful for Lightning nodes so that they can use Bitcoin Core in situations where they currently use Electrum.

   For example, an LSP has many mobile users who all connect to the LSP’s Electrum instance to get information on whether their funding/commitment transactions have confirmed, etc.

   Instead, they could be using the Core REST interface to retrieve this info, using gettxspendingprevout + @sstone’s PR.

   A caveat is that resolving this issue might not get us all the way to replacing Electrum, because Core still doesn’t support an address index, which is useful for monitoring initial on-chain deposits from users.

2. maflcko added the label RPC/REST/ZMQ on Nov 7, 2025
3. kevkevinpal referenced this in commit e287d145aa on Nov 17, 2025
4. kevkevinpal referenced this in commit af22ae8af1 on Nov 17, 2025
5. kevkevinpal referenced this in commit 924624ff22 on Nov 17, 2025
6. kevkevinpal referenced this in commit 57ca75a8b1 on Nov 17, 2025
7. 
   stickies-v commented at 11:26 am on March 20, 2026: contributor

   I know the REST interface requires less tooling to consume than the RPC interface, but would be helpful to better understand exactly why the gettxspendingprevout RPC does not suffice here? Is the JSON (de)serialization overhead unacceptable? I.e. is a REST equivalent a necessity, or a nice to have?

Contributors
valentinewallace stickies-v

Labels
RPC/REST/ZMQ