nymkappa
nymkappa
Unsure if that's an issue with lnd or our nodejs backend (or a combination of both with bad timings), but that's obviously incorrect. It happens when you go offline for...
Currently we refresh our db once per hour, let's increase that. Regarding stats (network wide and node focused), we can compute them every time, and only insert a new row...
The reason why the difficulty adjustment shows wrong number is because when you are offline for too long and restart your instance, mempool will fast forward to the latest synced...
Ideas we can draw upon - @wiz @softsimon ### btc.com  ### heatmap / github activity style  ### heatmap with different style  ### Hashrate + block found? 
Instead of sending an array of JSON object, containing hundreds of repeated fields name, switch to JSON arrays to make API response smaller (and faster).
Now that mining pools are stored into RAM when the database is disabled (see https://github.com/mempool/mempool/pull/1822), we should be able to display the full blocks list data set even if indexing...
Fixes https://github.com/mempool/mempool/issues/2570 ### Bitgo (does not advertise sockets) `03a9364a1f954fc146fdea379957aa778273d641805299d18cae5621563d541851` ### BJCR_BTCPayServer (advertises ipv4 only) `020003b9499a97c8dfbbab6b196319db37ba9c37bccb60477f3c867175f417988e` ### AlasPoorYorick (advertises tor only) `020016201d389a44840f1f33be29288952f67c8ef6b3f98726fda180b4185ca6e2`
In a previous PR, I've split tor only nodes and hybrid nodes (tor + clearnet), but I did not updated the chart. So the LN dashboard `Nodes` count does not...
Note: Don't forget skeletons