From: Tier Nolan <tier.nolan@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Fork of invalid blocks due to BIP66 violations
Date: Sun, 5 Jul 2015 02:32:16 +0100 [thread overview]
Message-ID: <CAE-z3OXX9wVCRiNHxpP3deTv63zOkJv4JDAYG8LXXOrFCoKVxg@mail.gmail.com> (raw)
In-Reply-To: <55986D44.20601@openbitcoinprivacyproject.org>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On Sun, Jul 5, 2015 at 12:33 AM, Justus Ranvier <
justus@openbitcoinprivacyproject•org> wrote:
> I think the problem is tractable if some reasonable assumptions are made
> about the ability of SPV clients to perform validity checks that don't
> involve any state outside a single transaction (or block):
>
> https://gist.github.com/justusranvier/451616fa4697b5f25f60
>
>
I agree, it is definitely tractable.
If Bitcoin was being designed from scratch, it could be made even easier.
As things stand, the extra commitment information needs to be added to
extra trees, which themselves need to be checked.
The "prover", in your example, should ideally store additional meta-data
along with each block.
If P2SH was made mandatory, then much of the transaction validation could
be performed on the transaction alone.
Both the signature and the public key would be included in the spending
transaction.
[-- Attachment #2: Type: text/html, Size: 1540 bytes --]
next prev parent reply other threads:[~2015-07-05 1:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 5:43 Raystonn
2015-07-04 5:44 ` Peter Todd
2015-07-04 15:18 ` Justus Ranvier
2015-07-04 15:35 ` Tier Nolan
2015-07-04 16:01 ` Justus Ranvier
2015-07-04 17:58 ` Tier Nolan
2015-07-04 23:33 ` Justus Ranvier
2015-07-05 1:32 ` Tier Nolan [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-04 5:46 Raystonn
2015-07-04 5:17 Raystonn
2015-07-04 5:22 ` Peter Todd
2015-07-04 5:40 ` odinn
2015-07-04 3:11 Raystonn
2015-07-04 3:17 ` Gregory Maxwell
2015-07-04 3:30 ` Peter Todd
2015-07-04 3:32 ` odinn
2015-07-04 10:04 ` Tier Nolan
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=CAE-z3OXX9wVCRiNHxpP3deTv63zOkJv4JDAYG8LXXOrFCoKVxg@mail.gmail.com \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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