📅 Original date posted:2011-12-22
🗒️ Summary of this message: A proposal for a hierarchical network where miners/supernodes are tightly interconnected at the top and lightweight clients verify transactions at the bottom.
📝 Original message: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 at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111222/b2825251/attachment.sig>;
Andy Parkins [ARCHIVE] /
npub1nx…7wjrv
2023-06-07 02:50:32
in reply to nevent1q…ktrs
Author Public Key
npub1nxlvf9mj3jzgue25n5d9y47s3h5hvg0ded9hwpejdxj9mtrs34vs97wjrvPublished at
2023-06-07 02:50:32Event JSON
{
"id": "55145b0817aad4a0d8768deb460f74a41545a3f4433bf6fb5f4148e1a0b758ef",
"pubkey": "99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59",
"created_at": 1686106232,
"kind": 1,
"tags": [
[
"e",
"4af0205fae641367dcfd78e02a7a0b6f75f880a1f702affe5d70f7b792eb8207",
"",
"root"
],
[
"e",
"7a4869077e8d88968caac4dfdd491775328a44875c9e75c22b07bef31804a1b0",
"",
"reply"
],
[
"p",
"a277336e95d2d0a831fff67fc80d8082322689a88ede9f877fa246a02629a43f"
]
],
"content": "📅 Original date posted:2011-12-22\n🗒️ Summary of this message: A proposal for a hierarchical network where miners/supernodes are tightly interconnected at the top and lightweight clients verify transactions at the bottom.\n📝 Original message:On 2011 December 21 Wednesday, Christian Decker wrote:\n\n\u003e Supernodes will be those nodes that verify all transactions and make them\n\u003e available to miners. Since miners will become more and more specialized\n\u003e these supernodes are likely to be owned by the miners themself. To be a\n\u003e miner either you need to verify all the transactions you include (otherwise\n\u003e others might be able to find an error in your block and thus drop it) or\n\u003e have someone that verifies them for you. In the end I think we'll end up\n\u003e with a hierarchical network, with the miners/supernodes tighly\n\u003e interconnected at the top and the lightweight clients that simply verify\n\u003e transactions (or their inputs to be precise) that are destined for them at\n\u003e the bottom.\n\nA thought occurred to me. We already run a decentralised system, but it's \ndone by making everyone duplicate all other work. There is no fundamental \nreason why all work needs to be duplicated though. What about this: every \nnode randomly chooses whether to verify any particular transaction. If we \nassume the network is large and the random factor is correctly chosen, then we \ncan still guarantee that every transaction is verified. Then, we simply add a \nprotocol message that is a negative-announce transaction. That is to say, we \ngive nodes a way of telling other nodes that they think a transaction is \ninvalid. The other nodes are then free to verify _that_ assertion and forward \nthe negative-announce.\n\nMiners can then listen for negative-announcements and use them to decide were \nto dedicate their verification efforts. They then don't need to verify all \n(or perhaps even any) transactions themselves and can dedicate their \nprocessing power to mining.\n\n(I've actually mentioned this idea before, but that time I was using it as a \ndouble-spend prevention method).\n\n\n\nAndy\n\n-- \nDr Andy Parkins\nandyparkins at gmail.com\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 198 bytes\nDesc: This is a digitally signed message part.\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111222/b2825251/attachment.sig\u003e",
"sig": "131eeacd5a086a5d92ebefa9319712b174f1bc8d54ca23824919f0bd0386adef3ddacc801beb329163a755427c71b1ff64e339f0e0e560df3c39eba9717562ce"
}