From: Tier Nolan <tier.nolan@gmail•com>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
Paul Rabahy <prabahy@gmail•com>
Subject: Re: [Bitcoin-development] Chain pruning
Date: Thu, 10 Apr 2014 21:12:00 +0100 [thread overview]
Message-ID: <CAE-z3OU0Y=ifGdaMKkSEJr38Rhq6pNfDeSUxF=ROiJ_0j3wh9Q@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBiRFJT6zC=7oMMzJuU-06oxgZ4Q-1kD+pCitw1JmAFs7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
On Thu, Apr 10, 2014 at 7:32 PM, Pieter Wuille <pieter.wuille@gmail•com>wrote:
> If you trust hashrate for determining which UTXO set is valid, a 51%
> attack becomes worse in that you can be made to believe a version of
> history which is in fact invalid.
>
If there are invalidation proofs, then this isn't strictly true.
If you are connected to 10 nodes and only 1 is honest, it can send you the
proof that your main chain is invalid.
For bad scripts, it shows you the input transaction for the invalid input
along with the merkle path to prove it is in a previous block.
For double spends, it could show the transaction which spent the output.
Double spends are pretty much the same as trying to spend non-existent
outputs anyway.
If the UTXO set commit was actually a merkle tree, then all updates could
be included.
Blocks could have extra data with the proofs that the UTXO set is being
updated correctly.
To update the UTXO set, you need the paths for all spent inputs.
It puts a large load on miners to keep things working, since they have to
run a full node.
If they commit the data to the chain, then SPV nodes can do local checking.
One of them will find invalid blocks eventually (even if one of the other
miners don't).
>
> --
> Pieter
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 2742 bytes --]
next prev parent reply other threads:[~2014-04-10 20:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 11:37 Mike Hearn
2014-04-10 11:57 ` Wladimir
2014-04-10 12:10 ` Gregory Maxwell
2014-04-10 14:19 ` Wladimir
2014-04-10 16:23 ` Brian Hoffman
2014-04-10 16:28 ` Mike Hearn
2014-04-10 16:47 ` Brian Hoffman
2014-04-10 16:54 ` Ricardo Filipe
2014-04-10 16:56 ` Brian Hoffman
2014-04-10 16:59 ` Pieter Wuille
2014-04-10 17:06 ` Brian Hoffman
2014-04-10 18:19 ` Paul Rabahy
2014-04-10 18:32 ` Pieter Wuille
2014-04-10 20:12 ` Tier Nolan [this message]
2014-04-10 20:29 ` Pieter Wuille
2014-04-10 19:36 ` Mark Friedenbach
2014-04-10 21:34 ` Jesus Cea
2014-04-10 22:15 ` Mark Friedenbach
2014-04-10 22:24 ` Jesus Cea
2014-04-10 22:33 ` Gregory Maxwell
2014-04-10 16:52 ` Ricardo Filipe
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-z3OU0Y=ifGdaMKkSEJr38Rhq6pNfDeSUxF=ROiJ_0j3wh9Q@mail.gmail.com' \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pieter.wuille@gmail$(echo .)com \
--cc=prabahy@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