Jeffro

I don't see any glaring issues with this PR as long as there are no name conflicts, which might be easier said than done. @mj-xmr Would you plan on eventually...

> However, I could imagine, that at point in the future, when maybe `wallet7` becomes nicely concept-separated, where each concept is put into a separate class and file, there might...

Yeah it's a really cool feature, and should be documented so people don't miss it, but I can imagine it could cause weird, hard to debug issues if it was...

@trasherdk the whole point of explicitly specifying exclusive nodes is to curate your list of connections. The node software shouldn't override that decision on its own because a connected node...

I have exactly the same problem as above, with the same software info as @snxraven. I can't connect to the dat network and clone anything outside of localhost. I am...

If a PR is to be created from this, make sure to also use hardcoded SSL certificates for said nodes

I think we should keep the public node list, but each entry must be verified by a chain of SSL certificates which is signed by one of a small set...

We could create an RPC command that retrieves a daemon's p2p public node list. So on start, the wallet runs the command `get_public_nodes` (or similar) on a *trusted* node, caches...

> Yes, it's possible for trusted community nodes to spy too, but the chance is way lower than when selecting a random node in the network. Yeah I'm saying that...

Why is this check redundant? If `start_block_index > 0`, then `(uint64_t) -start_block_index` is undefined.