s7r

The hack is good for now, but I think it's better to fully validate the v3 address in ElectrumX entirely. Just the length might not be enough in the future...

hm, I might not understand the question properly, but maybe not making mandatory for users to encode it will help? Like defaulting it to "something" unless explicitly configured? I think...

Negative, Python versions are not the same and your hint might make sense: Server not giving the error runs Python 3.7.0 (default, Sep 9 2018, 18:53:14) Server giving the error...

RIght. It is in Python 3.7 as well: project-management electrumx_server[7230]: INFO:PeerManager:[electrumx-core.1209k.com:50002 SSL] [Errno -9] error while attempting to bind on address ('MY_IPv4', 0): address family for hostname not supported Jan...

From initial digging it seams like this is triggered for peers that report a HOST that only resolves to IPv6 address, not dual-stacked ones (IPv4 and IPv6). Keeping an eye...

I catch also with peers that do not resolve to IPv6 only, and are not even dual-stacked (no IPv6 at all). This is for when a peer triggers it via...

yea I am getting it very heavily as well. I run multiple servers, on Python 3.7 I get it less often (but still get it) than on Python 3.6.x which...

The wording and behavior in #1085 makes a nicer user experience, for those who don't know or care what these expiration dates are and are not interested into changing them....

It might be useful to ask this at initial runtime (first setup) as a Yes/No question: `Would you like to allow duplicate clients to connect simultaneously (multiple connections from same...

@wid-get that's odd - on Debian Bullseye it works with `Before=network-online.target` , after every reboot all iptables and ip6tables rules are loaded fine. Wonder if it's something platform dependent?