Wrong patch? This looks like node.js code for something called txtool.
--
Michael
On Fri, Nov 22, 2013 at 1:46 PM, Jeff Garzik jgar...@bitpay.com wrote:
Trying something new... a [simple] patch sent to the list, for
discussion. Seems unlikely to be controversial. github access is
On Tue, Jul 23, 2013 at 4:36 AM, Pieter Wuille pieter.wui...@gmail.comwrote:
Apart from that, exposing this HTTP-based interface publicly has its
own problems, like security risks and potential DoS risks. If
anything, we should be reducing the attack surface rather than
increase it. IMHO, the
+1 and thank you. I've prototyped a couple different Bitcoin projects that
would benefit from this.
I'm traveling with poor 'net so I haven't read the patches yet. I echo pull
request comments about using Accept and Accept-Encoding headers. Same for
an API version number in the URL.
It'd be
On Mon, Jun 3, 2013 at 5:43 PM, Melvin Carvalho melvincarva...@gmail.comwrote:
Sorry if this is a stupid question, but why would someone want to
sacrifice their bitcoins?
Good question. One reason is https://en.bitcoin.it/wiki/Fidelity_bonds
Cheers,
Michael
On Fri, May 31, 2013 at 5:56 AM, Rune Kjær Svendsen runesv...@gmail.comwrote:
I have an application that wants to keep up with new blocks as they come
in. For that I can use the -blocknotify option with bitcoind, which will
execute my application for each new block.
The problem is that my
On Tue, Jan 31, 2012 at 12:17 AM, Gregory Maxwell gmaxw...@gmail.com wrote:
On Mon, Jan 30, 2012 at 11:33 PM, Michael Hendricks mich...@ndrix.org wrote:
address manager point to the attacker. If a client has 8 connections
to the network, a Sybil attack would succeed 1.7% of the time.
Meh
On Mon, Jan 30, 2012 at 7:05 PM, Gavin Andresen gavinandre...@gmail.com wrote:
Given the randomness in Pieter's design, that seems extremely unlikely
/ difficult to do. Is it possible to do a back-of-the-envelope
calculation to figure out what percentage of nodes on the network an
attacker
2011/11/17 Martinx - ジェームズ thiagocmarti...@gmail.com
Testing the 0.5.0 in Linux, I see a strange behaviour:
1- Open qt-client, blockchain stops the downloading at 10%... Wait 30
minutes... not reach 11%...
2- Close and reopen the qt-client, blockchain start again at 0%...
Normal!?
3-
8 matches
Mail list logo
