woofbot on Nostr: 🥳 New Version v0.9.6 🥳 - Important improvement to the logic that looks for ...
🥳 New Version v0.9.6 🥳
- Important improvement to the logic that looks for outgoing payments from watched addresses. If you watched addresses on a Raspberry-Pi and got many alerts like "your node was not synced for some time" - they happened because the logic was so inefficient that it couldn't keep up with the rate that new blocks were coming.
- Important improvement to the logic that watches whether the mempool is "clear" (all the transactions can fit in a single block). The old logic calculated the exact weight of the mempool every minute. Pulling the entire mempool is very slow when the mempool is nearly full (can take even 20-30 seconds). Instead, we now first call a simpler api `getmempoolinfo` which gives the mempool's "size without witness-data", from which we calculate a lower bound to the mempool "weight" (the difference between "size" and "weight" is explained here: https://en.bitcoin.it/wiki/Weight_units ). If the lower bound is too high (over 4M wu), we know that the mempool is not empty and don't need to calculate its exact weight. If the lower bound is low, calculating the exact weight of the mempool is easy and fast.
No new features this time, but if you're running a node on a Raspberry-Pi you'll feel a big difference. Many thanks to The Bitcoin Lizards for stress-testing the Bitcoin mempool.
- Important improvement to the logic that looks for outgoing payments from watched addresses. If you watched addresses on a Raspberry-Pi and got many alerts like "your node was not synced for some time" - they happened because the logic was so inefficient that it couldn't keep up with the rate that new blocks were coming.
- Important improvement to the logic that watches whether the mempool is "clear" (all the transactions can fit in a single block). The old logic calculated the exact weight of the mempool every minute. Pulling the entire mempool is very slow when the mempool is nearly full (can take even 20-30 seconds). Instead, we now first call a simpler api `getmempoolinfo` which gives the mempool's "size without witness-data", from which we calculate a lower bound to the mempool "weight" (the difference between "size" and "weight" is explained here: https://en.bitcoin.it/wiki/Weight_units ). If the lower bound is too high (over 4M wu), we know that the mempool is not empty and don't need to calculate its exact weight. If the lower bound is low, calculating the exact weight of the mempool is easy and fast.
No new features this time, but if you're running a node on a Raspberry-Pi you'll feel a big difference. Many thanks to The Bitcoin Lizards for stress-testing the Bitcoin mempool.