gt;
>
>
> --- On Mon, 4/30/12, Amir Taaki wrote:
>
> > From: Amir Taaki
> > Subject: Re: [Bitcoin-development] BIP to improve the availability of
> blocks
> > To: "bitcoin-development@lists.sourceforge.net" <
> bitcoin-development@lists.sourceforge.
m: Amir Taaki
> Subject: Re: [Bitcoin-development] BIP to improve the availability of blocks
> To: "bitcoin-development@lists.sourceforge.net"
>
> Date: Monday, April 30, 2012, 3:11 PM
> This is optimisation where it isn't
> needed. Bandwidth is not the bottleneck o
Now there are 2 code branches
that must be maintained - urgh.
From: Wladimir
To: Rebroad (sourceforge)
Cc: bitcoin-development@lists.sourceforge.net
Sent: Monday, April 30, 2012 7:26 PM
Subject: Re: [Bitcoin-development] BIP to improve the availability of blo
On Mon, Apr 30, 2012 at 6:40 PM, Rebroad (sourceforge) <
rebroad+sourceforge@gmail.com> wrote:
>
> My proposal is that in addition to the size (which is advertised in
> the header), the hash is also advertised in the header (of a block).
> This would help nodes to determine whether they wanted
Dear Bitcoin developers,
In brief, the proposal I have is to extend the protocol to allow
partial block download and upload. This is for people with
intermittent connectivity or restricted connectivity. e.g. my own
internet connection is quite slow, and my ISP routinely sends RSTs to
both sides of
5 matches
Mail list logo
