Re: [bitcoin-dev] BIP proposal: NODE_NETWORK_LIMITED service bits

2017-05-11 Thread Gregory Maxwell via bitcoin-dev
On Thu, May 11, 2017 at 3:13 PM, Jonas Schnelli via bitcoin-dev wrote: > Hi > > Currently, pruned peers have no way how to signal their (valuable) service. > A BIP proposal to improve this (draft): >

Re: [bitcoin-dev] BIP proposal: NODE_NETWORK_LIMITED service bits

2017-05-11 Thread Eric Voskuil via bitcoin-dev
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/11/2017 01:36 PM, Aymeric Vitte via bitcoin-dev wrote: > Sorry again, is this discussion really serious? > > In this thread, previous ones or others, the level of approximation > is obvious, often shadowed by useless maths/papers and strange

Re: [bitcoin-dev] BIP proposal: NODE_NETWORK_LIMITED service bits

2017-05-11 Thread Aymeric Vitte via bitcoin-dev
Sorry again, is this discussion really serious? In this thread, previous ones or others, the level of approximation is obvious, often shadowed by useless maths/papers and strange calculations that are not helping, at the end nobody knows what would happen "if", how far the chain can roll back,

Re: [bitcoin-dev] BIP proposal: NODE_NETWORK_LIMITED service bits

2017-05-11 Thread Jonas Schnelli via bitcoin-dev
> Is 49 days particularly useful? Would it be a problem to instead leave both- > bits undefined? I'm thinking this might be better as a way to indicate "7 > days, plus a deterministically chosen set of historical blocks"… I though two service bits allow three states and we should define all

Re: [bitcoin-dev] BIP proposal: NODE_NETWORK_LIMITED service bits

2017-05-11 Thread Luke Dashjr via bitcoin-dev
> A peer signaling NODE_NETWORK_LIMITED_LOW & NODE_NETWORK_LIMITED_HIGH MUST > be capable of serving at least the last 7'056 blocks (~49 days) > (NODE_NETWORK_LIMITED_HIGH's value ^2). Is 49 days particularly useful? Would it be a problem to instead leave both- bits undefined? I'm thinking this

Re: [bitcoin-dev] BIP proposal: NODE_NETWORK_LIMITED service bits

2017-05-11 Thread Gregory Maxwell via bitcoin-dev
It probably should be stated in terms of what you're promising to do-- 288 and 1152 blocks, not what we hope it will accomplish. Then advise clients to use peers with headroom because their estimates could be wrong and reorgs. Reorgs aren't the only concerns that drive larger numbers: The peak

[bitcoin-dev] BIP proposal: NODE_NETWORK_LIMITED service bits

2017-05-11 Thread Jonas Schnelli via bitcoin-dev
Hi Currently, pruned peers have no way how to signal their (valuable) service. A BIP proposal to improve this (draft): https://github.com/jonasschnelli/bips/wiki/NODE_NETWORK_LIMITED-BIP-DRAFT Feedback is highly