Author: Justus Ranvier 2015-03-17 16:26:10
Published on: 2015-03-17T16:26:10+00:00
The proposal suggests applying Freenet's "Darknet" technique to Bitcoin to reduce privacy leaks due to harvesting attacks. This would involve allowing Bitcoin nodes to create authenticated connections with trusted peers via CurveCP, so that nodes with at least one CurveCP peer only broadcast their transactions to those peers. The use of CurveCP requires both sides of the connection to know each other's long-term public key. To set up a secure connection between their nodes, users would first use an API command to generate their node references and exchange these files, copying them to the ~/.bitcoin/curvecp directory with a .ref extension. Instead of listening both for regular TCP and CurveCP connections on the same port, CurveCP connections would take place on a separate port designated by -bind_curvecp, -port_curvecp, and -externalip_curvecp. This proposal would work along with, or independently of, Tor usage. Currently, the only way to configure a node to submit its transactions anonymously to the network is to make the node non-listening, which means it cannot contribute to the network. The proposal would allow nodes to contribute to the network as listening nodes, while retaining privacy with regards to transactions originating from themselves. CurveCP connections can also be created between full nodes and SPV nodes, in which case transactions originating from the SPV peers would be routed as if they originated from the full node.
Updated on: 2023-06-09T18:53:51.537640+00:00