On 08/12/2017 01:12 PM, Jorge Timón wrote:
> Awesome! I didn't know those were implemented already. That must have
> been recent, but great.
There was a list post a while back, I copied you for code review. If you
still want to take a look please feel free.
> I don't understand the point about csv, does libbitcoin activate them at
> a fixed height?
BIP9 has a time window, which when is past precludes activation of the
associated rules at any future time (barring the sudden exposure of a
stronger chain that was mined with timestamps in the window but is not
currently known to exist). In other words, a sufficiently deep future
reorg would de-activate the rules. So (barring collision) the activation
is fixed at a single block hash/height. Height is insufficient because a
BIP9 would *not* activate on a deep future reorg.
> Is the plan to do the same fod segwit?
It depends on when the implementation ships. If after the SW window
effectively closes the same logic would hold, which may be the case.
e
> On 12 Aug 2017 23:01, "Eric Voskuil" <eric@???
> <mailto:eric@voskuil.org>> wrote:
>
> On 08/12/2017 12:44 PM, Jorge Timón wrote:
> > A simpler first step would be for libbitcoin to support bip113 and
> > bip68/bip112.
>
> These are implemented in v3.3.0.
>
> > Ideally by also implementing bip9 for sf activation, which
> > could be used for segwit too.
>
> Since bip9 cannot reactivate after its window closes there is no reason
> to implement it for CSV.
>
> e
>
> > On 10 Aug 2017 21:09, "Eric Voskuil" wrote:
> > On Aug 10, 2017, at 5:00 AM, Luke Dashjr wrote:
> >> On Thursday 10 August 2017 11:46:23 AM
> mlmikael@??? <mailto:mlmikael@openmailbox.org> wrote:
> >>> The logics will kick in in 12 days ( https://xbt.eu ) so I
> guess.. in
> >>> absence of Segwit, libbitcoin deployments will fork off the main
> >>> chain and
> >>> also be unable to make transactions, until Segwit is
> implemented?
> >>
> >> Segwit is a softfork, so old nodes will continue to operate fine,
> >> just with a
> >> loss of full-node security. But alternative implementations never
> >> quite have full-node security anyway simply because they can't be
> >> guaranteed to enforce the rules exactly.
> >
> > https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki
> <https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki>
> >
> <https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki
> <https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki>>
> >
> >> That being said, it would be a good idea for libbitcoin to update
> >> so its
> >> wallet can take advantage of the new features.
> >
> > Pull requests welcome.
> >
> > e
>
::
Re: [Libbitcoin] What about Segwit?…
