From: Tomas <tomas@tomasvdw•nl>
To: Bryan Bishop <kanzure@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Non-confirming block signalling
Date: Fri, 05 May 2017 15:09:17 +0200 [thread overview]
Message-ID: <1493989757.1477512.966870152.4C72B056@webmail.messagingengine.com> (raw)
[-- 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 --]
next reply other threads:[~2017-05-05 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 13:09 Tomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-05 11:24 Tomas
2017-05-05 13:01 ` Bryan Bishop
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=1493989757.1477512.966870152.4C72B056@webmail.messagingengine.com \
--to=tomas@tomasvdw$(echo .)nl \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kanzure@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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