Roman Zeyde
Roman Zeyde
Looks great, the usage is indeed much simpler :)
Sounds great - let's try using them :)
Sounds good, but I prefer adding it when https://github.com/spesmilo/electrumx/pull/90 is officially merged.
Please note that the [`outpoint-rpc` branch](https://github.com/romanz/electrs/commits/outpoint-rpc) doesn't implement the notification mechanism specified here: https://github.com/spesmilo/electrumx/pull/90/files#diff-ffa7e37c618564f8c58d9072b5ef234e6e9b2cdf1d71d16be7dc356146cb475fR648-R655 It was a "WIP" implementation that I put on hold, waiting for the official Electrum 1.5...
Many thanks for the contribution! I have pushed a bit different implementation at #454, including the subscription and notification mechanism.
Thanks for reporting this issue! electrs fee estimation works by inspecting the node's mempool transaction fee bands, similar to how they are shown in https://jochen-hoenicke.de/queue/ or https://mempool.space/graphs. The main issue...
The suggestion sounds good - although I am not using systemd for electrs, I guess it should help many other users. I'll be happy to help with review and tests...
I agree with "Warn, continue with systemd" - but we should make sure the warning is verbose & clear enough to understand what went is wrong, and how it should...
Sounds good, let's do it for `next` branch.
I'm not sure that there is a way to bind a single socket to a subset of your network interfaces: https://stackoverflow.com/questions/12709771/how-to-bind-a-socket-to-multiple-interfaces Does binding to all interfaces ("0.0.0.0") may work for...