Re: [Bitcoin-development] Abnormally Large Tor node accepting only Bitcoin traffic

2014-07-27 Thread Michael Wozniak
It’s in my logs: 2014-07-28 02:00:24 receive version message: /Satoshi:0.9.2/: version 70002, blocks=302684, us=**:8333, them=0.0.0.0:0, peer=5.9.93.101:33928 On Jul 27, 2014, at 10:45 PM, Gregory Maxwell gmaxw...@gmail.com wrote: On Sun, Jul 27, 2014 at 7:40 PM, Peter Todd

Re: [Bitcoin-development] BIP 38 NFC normalisation issue

2014-07-15 Thread Michael Wozniak
I have a python implementation that seems to pass this test vector: https://github.com/wozz/electrum/blob/bip38_import/lib/bip38.py#L299 On Jul 15, 2014, at 9:19 AM, Andreas Schildbach andr...@schildbach.de wrote: I think generally control-characters (such as \u) should be disallowed in

Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments

2014-07-01 Thread Michael Wozniak
support it. - Michael Wozniak On Jul 1, 2014, at 5:48 AM, Andreas Schildbach andr...@schildbach.de wrote: On 07/01/2014 10:18 AM, Mike Hearn wrote: ​However it's not ideal at the moment. Basically the main problem is that in the BIP72 there is no way to provide a fallback alternative URI

Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments

2014-07-01 Thread Michael Wozniak
familiar with the Electrum implementation, which is currently checking for any duplicate parameters and treating the entire URI as invalid if duplicate parameters exist (following the parameter pollution suggestions). - Michael Wozniak On Jul 1, 2014, at 10:59 AM, Andreas Schildbach andr

Re: [Bitcoin-development] DNS seeds unstable

2014-05-19 Thread Michael Wozniak
a custom proxy application. - Michael Wozniak On May 19, 2014, at 4:14 PM, Alex Kotenko alexy...@gmail.com wrote: Hmm, I've mostly setup what's promised, testing DNS seeds now. There is one problem I see that I can't really solve myself. This dnsseed daemon cannot serve more than one name

Re: [Bitcoin-development] DNS seeds unstable

2014-05-19 Thread Michael Wozniak
You would set it up as a forwarder, not as a zone transfer to bind. That should proxy the request every time and only cache based on any TTL that’s set in the response. Here’s an example of how it could work: