pull down to refresh

bitcoin-submittx, improvedgithub.com/AndySchroder/bitcoin-submittx
275 sats \ 4 comments \ @andy 16h bitcoin
  • TOR stream isolation.
  • Switch to PySocks.
  • Auto fetch peers from DNS seeds.
  • Scan a QR code of a signed transaction from Sparrow Wallet.
  • Optionally accept transaction from STDIN and not the command line.
  • Selectable logging levels.
  • Installable via pip.
  • General code cleanup and usability improvements.
  • Remove shitcoinery.
write
preview
related posts
101 sats \ 3 replies \ @random_ 16h
TOR stream isolation.
Don't know how to test if the TOR stream isolation is actually working properly, but it should be.
This does not inspire confidence.
Maybe if you put it in a docker container, you can guarantee stream isolation? idk
reply
1 sat \ 2 replies \ @andy OP 16h
Not sure that docker is really needed to resolve this.
The way to test stream isolation would be to have several nodes that you control as test nodes, then use this tool with the --nodes option and explicitly connect to them, then monitor their logs and see where they saw connections from and make sure they don't come from the same IP. The problem is that bitcoin-submittx makes such short lived connections it will be a bit trickier to test.
I have not setup this test case yet, so maybe a better comment would have been that I haven't tested it, rather than I don't know how to.
reply
101 sats \ 1 reply \ @random_ 16h
I just wouldn't claim it as the first bullet point in your list of improvements if you're not certain it works.
It calls into question everything else imo.
Am I crazy?
reply
50 sats \ 0 replies \ @andy OP 15h
Just trying to be honest. Would love for someone to scrutinize it from a technical perspective. See https://github.com/AndySchroder/bitcoin-submittx/blob/efa47eb1ac436cbb4fccbff64567ea1c52fe6352/bitcoin-submittx#L152-L156 for where I try to enable TOR stream isolation. A link is referenced that suggests that is how I should do it.
reply