> > So my suggestion for the next steps are:
> >
> > - Update BIP173 to include the insertion weakness as an erratum, and
> > the results of this analysis.
> >
>
> To clarify, this step does not modify anything about the implementation of
> BIP173, only adds this as an additional erratum sec
Good morning Pieter,
> Hi all,
>
> I've made a writeup on Bech32's detection abilities, analysing how it
> behaves in the presence of not just substitution errors, but also
> swapping of characters, and insertions and deletions:
> https://gist.github.com/sipa/a9845b37c1b298a7301c33a04090b2eb
>
> I
Hi all,
I've made a writeup on Bech32's detection abilities, analysing how it
behaves in the presence of not just substitution errors, but also
swapping of characters, and insertions and deletions:
https://gist.github.com/sipa/a9845b37c1b298a7301c33a04090b2eb
It shows that the "insert or delete a
Hi Runchao,
- 1st question regarding double spending:
We won't allow a miner to sacrifice coinbase reward as much as possible for
a practical system. This will be achieved by setting a dynamic upper bound
for the number of rewards the miner could sacrifice. The upper bound would
be related to the
