-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We have BIP70 already in use (over a hundred paid requests).
Could you elaborate on why this needs changing?
On 28-04-14 14:39, Gavin Andresen wrote:
> There is a discussion about clarifying how BIP70 signs payment
> requests here: https://github.c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We rebroadcast incoming transactions without fees at several nodes,
including bc.info, to keep them in mempools.
On 01/17/2014 10:04 PM, Mark Friedenbach wrote:
> CPFP is *extremely* important. People have lost money because this
> feature is missing
Thanks a lot! I will run these patches on some nodes tomorrow to see if
it works.
On 22-11-13 21:49, Jeff Garzik wrote:
> Whitelist nodes against banning.
>
>
>
> --
> Shape the Mobile Experience: Free Subscription
> So
bounty++
On 06-11-13 06:33, kjj wrote:
> One of the things that really gets me going is when someone devises a
> model, tests it against itself, and then pretends that they've learned
> something about the real world.
>
> Naturally, the Selfish Mining paper is exactly this sort of nonsense.
>
On 08/07/2013 11:10 PM, Gavin Andresen wrote:
> I'd also like to hear from merchants: any issue with your payment
> processing server having "broadcast transaction" functionality?
>
On the contrary, we would prefer to broadcast the transaction ourselves.
Abe is able to do what you want.
https://github.com/jtobey/bitcoin-abe
https://bitcointalk.org/index.php?topic=22785.0
With kind regards,
Jouke Hofman
Bitonic.nl
On 06/06/2013 02:53 AM, Marko Otbalkana wrote:
> Could anyone point me to work/project(s) related to storing the block
> ch
We do automatic refunds. When bitcoins arrive after an offer has expired
(which happens quite often with webwallets that don't broadcast
transactions immediately), we return all the bitcoins to a specified
bitcoin-address. This happens a couple of times per day and can amount
to a couple of hundred
7 matches
Mail list logo
