Fix proxy support

[braydonf]

See bcoin-org/bsocks#1
Closes #206

[pinheadmz]

Tested with and without the bsocks patch braydonf/bsocks@40fa1f1.

Got the same error without:
RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 6. Received 8

No issues with the patch, tested by proxy-ing through tor:

bcoin --prefix=/Volumes/Serenity/proxy_test_10-10-19 --proxy=:<pw>@127.0.0.1:9150 --onion

As a side note, I wonder if proxy info should be reported in the RPC:

$  bcoin-cli rpc getnetworkinfo
{
  "version": "2.0.0-dev",
  "subversion": "/bcoin:2.0.0-dev/",
  "protocolversion": 70015,
  "localservices": "00000009",
  "localservicenames": [
    "NETWORK",
    "WITNESS"
  ],
  "localrelay": true,
  "timeoffset": -1,
  "networkactive": true,
  "connections": 7,
  "networks": [],
  "relayfee": 0.00001,
  "incrementalfee": 0,
  "localaddresses": [],
  "warnings": ""
}

[braydonf]

@pinheadmz Note: --proxy and --onion currently do not work together. That will need to be another fix.

[pinheadmz]

I noticed that - all peers were clearnet addresses, but traffic was still routing through the tor proxy.

[braydonf]

Yeah, technically with --proxy can have .onion hosts. However, the current addr format only supports the shorter v2 .onion hosts, there is a BIP proposal for addrv2. There would need to be an option to limit to only .onion for outgoing to achieve that, and then seed with some .onion hosts and then receive new addr messages for other hosts. The --onion option should enable incoming connections via an .onion address; however will need to listen on a different port than used for outgoing for the proxy.

[pinheadmz]

Ah, gotcha. I also tried adding onion peers (from bitcoind's seed list) and was able to connect:

bcoin-cli rpc addnode 2bfsxzluysybysnr.onion:8333 add

[Trimninja47]

This is really as close as I've been having a solution. But I still can't implement the process the right way. Is there anyone that can help me through this?