Sef Boukenken

> Does this handle torv3 addresses? > > I also think the new addrmgr.NetAddress belongs in `wire` as NetAddressV2. @dajohi No, torv3 addresses are not supported or broadcast in this...

Converting this to a draft until https://github.com/decred/dcrd/pull/2596 is merged, since this pull request builds on that.

Picking this one up.

> This would be a nice option. If it's still conceptually alright by jrick I expect you'll need to resolve a couple years of conflicts @sefbkn Alright, no problem.

Can I take this issue?

In the case where change would be dust, should the operation be considered valid? Giving dust-change to the miner seems to conflict with the expected behavior of the recipient fully...

@maxima120 Do you have any code I can test with, or a stack trace? I'm not aware of any size limitations at the web socket level, so a bit more...

@markwkjr That would be fantastic.

What is the driving use case, and what kind of data needs be stored for how long? I'm guessing the need to sync/sort unanchored hashes across multiple servers, possibly cache...