Jeremy Andrews

I opened Litecoin-Qt and asked for a new testnet bech32 address from the UI: ``` # ./litecoin-0.16.3/bin/litecoin-cli validateaddress tltc1qd9hf4rh9zlrdxqwvqwa88nq67pzz0agstxmql6 { "isvalid": true, "address": "tltc1qd9hf4rh9zlrdxqwvqwa88nq67pzz0agstxmql6", "scriptPubKey": "0014696e9a8ee517c6d301cc03ba73cc1af04427f510", "ismine": false, "iswatchonly": false,...

main network human-readable part: https://github.com/litecoin-project/litecoin/blob/master/src/chainparams.cpp#L142 testnet human-readable part: https://github.com/litecoin-project/litecoin/blob/master/src/chainparams.cpp#L247

Fixing the hrp seems to be all that's required. Patching the latest release: ``` diff --git a/pycoin/networks/all.py b/pycoin/networks/all.py index 226672d..e245188 100644 --- a/pycoin/networks/all.py +++ b/pycoin/networks/all.py @@ -39,7 +39,7 @@ BUILT_IN_NETWORKS...

I've reworked my codebase so I set defaults manually when not otherwise set, instead of relying on gumdrop for this. It was not because of this issue, it was because...

> In theory, the Rust wrapper is supposed to do the resource deallocation for you. As in, we specifically override the drop constructor to deallocate the model. So is there...

Thanks! This is very helpful. We're still getting organized on our end; @bdragon28 will reply soon.

And `netstat` showing that indeed it's incorrectly creating an IPv6 socket: ``` $ netstat -an | grep 1234 tcp6 0 0 127.0.0.1:1234 :::* LISTEN ```

Ah, I see. So it is creating an IPv4 socket, it's just creating an IPv6 socket as well. It seems my problem is different than I thought, then -- `recv_msg()`...

Adding the ability to to create a report from a single run or from multiple runs would be interesting. Happy to review your PR!

Merge conflict needs to be resolved