On Fri, May 25, 2018 at 6:42 PM, Gregory Maxwell wrote:
> configuration is roughly right, then M=1569861 and rice parameter 19
> should be used.
That should have been M=784931 B=19 ... paste error.
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfo
On Fri, May 25, 2018 at 5:54 PM, Pieter Wuille via bitcoin-dev
wrote:
> Hi all,
>
> I spent some time working out the optimal parameter selection for the
> Golomb Coded Sets that are proposed in BIP158:
> https://gist.github.com/sipa/576d5f09c3b86c3b1b75598d799fc845
>
> TL;DR: if we really want an
Hi all,
I spent some time working out the optimal parameter selection for the
Golomb Coded Sets that are proposed in BIP158:
https://gist.github.com/sipa/576d5f09c3b86c3b1b75598d799fc845
TL;DR: if we really want an FP rate of exactly 1 in 2^20, the Rice
parameter should be 19, not 20. If we don't
> On 24 May 2018, at 10:08 AM, Gregory Maxwell via bitcoin-dev
> wrote:
>
> On Thu, May 24, 2018 at 1:58 AM, Pieter Wuille via bitcoin-dev
> wrote:
>> Thanks everyone who commented so far, but let me clarify the context
>> of this question first a bit more to avoid getting into the weeds too
While you have rescind your concern, I’d like to point out that it’s strictly a
problem of SIGHASH_NOINPUT, not graftroot (or script delegation in general).
For example, we could modify graftroot. Instead of signing the (script), we
require it to sign (outpoint | script). That means a graftroot
