There are currently 2 ways to specify nodes to connect to.
"-connect" means connect to those nodes and no others.
"-addnode" means connect to those nodes initially, but you can connect to others too.
In both cases, the client will disconnect if the node "misbehaves".
This means that a proxy cannot be used, unless it also verifies all blocks.
Local network addresses won't be disconnect, even if they misbehave. However, this isn't the case for non-local.
If there was a command like "-setproxy", then this could be rectified. The client would connect to the proxy and would not disconnect, even if the proxy misbehaves.
An improvement would be a "misbehaved" message that says that certain messages count as misbehaving. That would allow the proxy to disconnect the peers it got the messages from. This would only be sent to proxies.
Maybe
int: severity (in percentage)
hash: hash of message
The proxy could remember the hashes for the messages it sent to the client.
A workaround is to run the proxy on the same computer as the client, so it gets an exemption.
Topic: Proxy operation (Read 631 times)
Jump to: