You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We run BitcoinJ over Tor with its built in Tor support (Orchid). As we use a native Tor instance for the P2P network it would be better to route BitcoinJ over our jTorProxy.
BitcoinJ uses nio (netty) which does not provide an API for sockets, so that might be difficult to get it working with Socks5Proxy. But it also supports a non nio BlockingClientManager which is also used for when BitcoinJ run over Tor.
We would need to pass our socket (or socketFactory) to a BlockingClientManager.
We maintain our own fork (https://github.com/bitsquare/bitcoinj) of BitcoinJ so changes should be added there.
The text was updated successfully, but these errors were encountered:
We run BitcoinJ over Tor with its built in Tor support (Orchid). As we use a native Tor instance for the P2P network it would be better to route BitcoinJ over our jTorProxy.
BitcoinJ uses nio (netty) which does not provide an API for sockets, so that might be difficult to get it working with Socks5Proxy. But it also supports a non nio BlockingClientManager which is also used for when BitcoinJ run over Tor.
We would need to pass our socket (or socketFactory) to a BlockingClientManager.
We maintain our own fork (https://github.com/bitsquare/bitcoinj) of BitcoinJ so changes should be added there.
The text was updated successfully, but these errors were encountered: