From: "Michael Grønager" <gronager@ceptacle•com>
To: Andy Parkins <andyparkins@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Protocol extensions
Date: Thu, 22 Dec 2011 11:27:32 +0100 [thread overview]
Message-ID: <23F92B83-4E96-401B-8A1C-3E6FE9DD8A8B@ceptacle.com> (raw)
In-Reply-To: <201112221012.55565.andyparkins@gmail.com>
It is analog to getting assigned a random part (based on IP) of the hashspace and then only verify transactions within this fraction.
But, there is in fact a subtle difference: If anyone can choose to verify at random, you will see lazy implementations where random means none, and as it is random you cannot, from the outside, judge if a node is taking part in the validation work or if it just benefitting from others announcements. In the hash space part, you can monitor peers and see if they did not tell you about a failed validation and then disconnect from them as they are either malicious or lazy.
Besides from that, I like a setup where we scream about failed verifications, but keep a low profile on things that actually verifies...
/M
On 22/12/2011, at 11:12, Andy Parkins wrote:
> On 2011 December 21 Wednesday, Christian Decker wrote:
>
>> Supernodes will be those nodes that verify all transactions and make them
>> available to miners. Since miners will become more and more specialized
>> these supernodes are likely to be owned by the miners themself. To be a
>> miner either you need to verify all the transactions you include (otherwise
>> others might be able to find an error in your block and thus drop it) or
>> have someone that verifies them for you. In the end I think we'll end up
>> with a hierarchical network, with the miners/supernodes tighly
>> interconnected at the top and the lightweight clients that simply verify
>> transactions (or their inputs to be precise) that are destined for them at
>> the bottom.
>
> A thought occurred to me. We already run a decentralised system, but it's
> done by making everyone duplicate all other work. There is no fundamental
> reason why all work needs to be duplicated though. What about this: every
> node randomly chooses whether to verify any particular transaction. If we
> assume the network is large and the random factor is correctly chosen, then we
> can still guarantee that every transaction is verified. Then, we simply add a
> protocol message that is a negative-announce transaction. That is to say, we
> give nodes a way of telling other nodes that they think a transaction is
> invalid. The other nodes are then free to verify _that_ assertion and forward
> the negative-announce.
>
> Miners can then listen for negative-announcements and use them to decide were
> to dedicate their verification efforts. They then don't need to verify all
> (or perhaps even any) transactions themselves and can dedicate their
> processing power to mining.
>
> (I've actually mentioned this idea before, but that time I was using it as a
> double-spend prevention method).
>
>
>
> Andy
>
> --
> Dr Andy Parkins
> andyparkins@gmail•com
next prev parent reply other threads:[~2011-12-22 10:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 7:41 Eric Lombrozo
2011-12-17 13:13 ` Michael Grønager
2011-12-17 13:37 ` Christian Decker
[not found] ` <CABsx9T0puk3CWH1cfNHMSVEoCPaLJJWNJ+H5ObCERZrzMbrTyA@mail.gmail.com>
2011-12-17 19:06 ` Gavin Andresen
2011-12-17 21:49 ` theymos
2011-12-18 0:44 ` Jordan Mack
2011-12-18 1:07 ` Jeff Garzik
2011-12-18 1:27 ` Jordan Mack
2011-12-18 14:16 ` Andy Parkins
2011-12-18 17:09 ` theymos
2011-12-18 18:06 ` Alan Reiner
2011-12-18 18:47 ` Amir Taaki
2011-12-18 19:37 ` Jorge Timón
2011-12-17 19:28 ` Gregory Maxwell
2011-12-17 20:34 ` Christian Decker
2011-12-18 21:19 ` Stefan Thomas
2011-12-19 21:43 ` Jordan Mack
2011-12-20 9:10 ` Wladimir
2011-12-20 10:44 ` Nicolas Fischer
2011-12-21 0:47 ` Kyle Henderson
2011-12-21 8:50 ` Michael Grønager
2011-12-21 11:42 ` Eric Lombrozo
2011-12-21 12:41 ` Michael Grønager
2011-12-21 16:10 ` Christian Decker
2011-12-22 9:18 ` Michael Grønager
2011-12-22 10:12 ` Andy Parkins
2011-12-22 10:27 ` Michael Grønager [this message]
2011-12-22 11:52 ` Andy Parkins
2011-12-22 12:14 ` Joel Joonatan Kaartinen
2011-12-22 12:26 ` Christian Decker
2011-12-22 12:42 ` Michael Grønager
2011-12-22 14:46 ` Andy Parkins
2011-12-25 2:55 ` Zell Faze
2011-12-21 17:17 ` Jordan Mack
2011-12-22 9:19 ` Michael Grønager
2011-12-21 6:19 Eric Lombrozo
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=23F92B83-4E96-401B-8A1C-3E6FE9DD8A8B@ceptacle.com \
--to=gronager@ceptacle$(echo .)com \
--cc=andyparkins@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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