From: Tomas <tomas@tomasvdw.nl>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Non-confirming block signalling
Date: Fri, 05 May 2017 13:24:49 +0200 [thread overview]
Message-ID: <1493983489.1448140.966773912.17FBAAC0@webmail.messagingengine.com> (raw)
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
next reply other threads:[~2017-05-05 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 11:24 Tomas [this message]
2017-05-05 13:01 ` [bitcoin-dev] Non-confirming block signalling Bryan Bishop
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=1493983489.1448140.966773912.17FBAAC0@webmail.messagingengine.com \
--to=tomas@tomasvdw.nl \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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