LearnBitcoin

Bitcoin Dev Archive 2017

Non-confirming block signalling

3 messages, 5 May 2017. Started by Tomas.

Tomas (2), Bryan Bishop

Permalink Original thread on gnusha.org

Tomas permalink original

I propose a method to mark blocks to indicate that they were generated without verifying the previous block. This can be done by using a bit of the version field.

This would counter the reduction of security caused by what is known as "SPV-mining".

The BIP is here: https://github.com/tomasvdw/bips/blob/master/bip-non-confirming-block-signalling.mediawiki

Tomas bitcrust

Bryan Bishop in reply to Tomas permalink original

On Fri, May 5, 2017 at 6:24 AM, Tomas via bitcoin-dev < bitcoin-dev@lists•linuxfoundation•org> wrote:

Quoted text (4 lines)
> I propose a method to mark blocks to indicate that they were generated
> without verifying the previous block. This can be done by using a bit of
> the version field.
>

see also: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011853.html

- Bryan http://heybryan.org/ 1 512 203 0507

Tomas in reply to Tomas permalink original

Sorry, I wasn't aware. This is indeed the same proposal.

On Fri, May 5, 2017, at 15:01, Bryan Bishop wrote:

Quoted text (10 lines)
> On Fri, May 5, 2017 at 6:24 AM, Tomas via bitcoin-dev <bitcoin-
> dev@lists•linuxfoundation•org> wrote:>> I propose a method to mark blocks to indicate that they were
>> generated>> without verifying the previous block. This can be done by using
>> a bit of>> the version field.
>
> see also:
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011853.html>
> - Bryan
> http://heybryan.org/
> 1 512 203 0507