Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GET `/liquid/api/address/<address>/utxo` returns "Too many history entries" without any possiblity of paging

See original GitHub issue

Here is an address I just grabbed of the UI where this happens:

❯ curl
Too many history entries%                                                                                                                                                                                                                                      

Is there a way of how I can still access the UTXOs?

Issue Analytics

  • State:open
  • Created 3 years ago
  • Comments:6

github_iconTop GitHub Comments

shesekcommented, Jul 26, 2021

Not easily I’m afraid, the way the utxo database is currently structured is incompatible with (efficient) paging and doesn’t work well when the per-address utxo set is huge. Making this work would require some re-designing, which might be done some day, but is not currently prioritized.

shesekcommented, Dec 4, 2020

I’m afraid that this accessing the UTXO set of “too popular” addresses is currently not possible. This might be revisited in the future.

The only thing you could do today is get the transaction history, which doesn’t have a “too popular” limit, and figure out the current UTXO set based on that. One way to do that is with two passes over the transaction list, one to populate a set of (txid,vout,amount) for every funded output, and a second pass to remove the outputs spent by the inputs.

(If tx A spends tx B and they both confirm in the same block, its possible for the spending tx A to appear in the transaction history list before the parent tx B that creates the spent output. Doing two passes is a simple way to deal with this, though not the most efficient one.)

Read more comments on GitHub >

github_iconTop Results From Across the Web

Operating Systems: Virtual Memory
The basic idea behind paging is that when a process is swapped in, the pager only loads into memory those pages that it...
Read more >
How to remove a single line from history? - Unix Stack Exchange
To delete or clear all the entries from bash history, use the history command below with the -c option. $ history -c. Alternatively,...
Read more >
OS monitors page-fault rate of each process to decide if ... - Body
Goal: Allocate enough frames to keep all pages used in the current locality of references without allocating too many page frames. The OS...
Read more >
Demand Paging - UCSD CSE
This model for a system's memory is called the memory hierarchy. Overlays. The oldest form of virtual memory is called the overlay. With...
Read more >
Virtual Memory and Paging - Operating Systems
table in the MMU with as many ... Page tables contain an entry for each virtual table ... When virtual pages are too...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found