Re: [bitcoin-dev] Non-confirming block signalling

Re: [bitcoin-dev] Non-confirming block signalling

[Tomas]

[-- Attachment #1: Type: text/plain, Size: 544 bytes --]

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



On Fri, May 5, 2017, at 15:01, Bryan Bishop wrote:
> 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


[-- Attachment #2: Type: text/html, Size: 1385 bytes --]

[bitcoin-dev] Non-confirming block signalling

[Tomas]

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

Re: [bitcoin-dev] Non-confirming block signalling

[Bryan Bishop]

[-- Attachment #1: Type: text/plain, Size: 412 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1062 bytes --]