Create account

Simon Van Gelder
replied 1638d
Use the local node for reading posts, submit the signed TXs to someone else's node (or use on online TX Push service).
replied 1637d
I'd be worried an ISP could see you send the transaction by SSL to a server . . if it was connected to that server's node, it might notice the node immediately send out that trx to oth
replied 1637d
I'm not sure how distinct they are, because once your ISP knows you are sending BCH TXs, they can block them. The problem is at the node level though, not the client.
Simon Van Gelder
replied 1637d
If the connection is encrypted, the ISP can't see the content, just that there is a connection (until they go full MITM for "National Security" reasons).
replied 1637d
Also, another idea is to always be sending data back and forth to the encrypted node, that way it's harder to tell when you actually did a TX.
replied 1637d
er nodes and be able to link the two events. So I think Tor would still be required for transmitting transactions privately, maybe even with some kind of random delay parameter.

It's
replied 1637d
an interesting problem to solve, but I think Member's first priority will be to ensure uncensorability, privacy second. While there is some overlap, they are also distinct objectives.