[REQUEST] please support ipv6 for masternode

[encryptblockr]

Current masternode setup only supports ipv4
As one of the leading crypto currencies on the market, will be great to support ipv6

Thanks

[UdjinM6]

This was discussed many times on dash.org/forum.

TL;DR: not sooner the IPv6 adoption rises to some meaningful levels, see https://www.google.com/intl/en/ipv6/statistics.html etc. OR when we drop everything that requires direct IP access to masternodes (like mixing) OR when we switch to some kind of custom routing for such cases (which is going to be slower and require more traffic IMO).

[encryptblockr]

@UdjinM6

other MN coins using ipv6
so i don't get where the complexity is coming from?
should be able to support ipv4, ipv6, and tor

[schinzelh]

Did you even take the time to read into the discussions WHY masternode entries other than IPv4 are not supported?

The complexity comes from the fact the you are not able to properly route between the different networks without the help of another overlay network - which none of the coins has afaik.

E.g. tell me: How is a IPv4-only connected wallet supposed to connect to a Tor listed masternode during mixing?

We are well aware that 150 MN coins copied our masternode code and re-enabled IPv6/Tor list entries, but they do not actually use these entries for something useful.

But maybe you know something we don't know, so: What "other MN coin" is actually using the nodes for something different than locking up coins and have them idling around?

[nmarley]

Technical discussion on the issue here: #1065

TL;DR: the Dash team didn't want to have to disable ipv6 for MNs, but there are technical reasons this change was made, and it was for the health of the network (as @schinzelh said, ipv4 only nodes couldn't connect to ipv6 nodes). With ipv4-only as it is now, all MNs are able to provide a benefit to the entire network (not just ipv6 nodes).

[nmarley]

Closing issue as it's a duplicate and this is a known, intentional Dash network architecture decision.