From: Bryan Bishop <kanzure@gmail.com>
To: Tomas <tomas@tomasvdw.nl>, Bryan Bishop <kanzure@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Non-confirming block signalling
Date: Fri, 5 May 2017 08:01:40 -0500 [thread overview]
Message-ID: <CABaSBawLB+igz0Za18Risp1nhhG5s07Bv0jwKzqpXR=iq2kPiw@mail.gmail.com> (raw)
In-Reply-To: <1493983489.1448140.966773912.17FBAAC0@webmail.messagingengine.com>
[-- 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 --]
next prev parent reply other threads:[~2017-05-05 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 11:24 [bitcoin-dev] Non-confirming block signalling Tomas
2017-05-05 13:01 ` Bryan Bishop [this message]
2017-05-05 13:09 Tomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABaSBawLB+igz0Za18Risp1nhhG5s07Bv0jwKzqpXR=iq2kPiw@mail.gmail.com' \
--to=kanzure@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=tomas@tomasvdw.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox