š
Original date posted:2015-12-08
š Original message:If partition is selected from a random key (the hash of the output for
example) then payment recipients would need to operate a full node on
each of the chains.
What's the point of partitioning if virtually everybody needs to operate
each partition?
The mining aspect has it's own set of issues, but I'm not going to get
into those.
On 12/08/2015 01:23 PM, Akiva Lichtner wrote:
> It's true that miners would have to be prepared to work on any
> partition. I don't see where the number affects defeating double
> spending, what matters is the nonce in the block that keeps the next
> successful miner random.
>
> I expect that the number of miners would be ten times larger as well,
> so an attacker would have no advantage working on one partition.
>
> On Tue, Dec 8, 2015 at 3:50 PM, Patrick Strateman via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org
> <mailto:bitcoin-dev at lists.linuxfoundation.org>> wrote:
>
> Payment recipients would need to operate a daemon for each chain,
> thus guaranteeing no scaling advantage.
>
> (There are other issues, but I believe that to be enough of a show
> stopper not to continue).
>
> On 12/08/2015 08:27 AM, Akiva Lichtner via bitcoin-dev wrote:
>> Hello,
>>
>> I am seeking some expert feedback on an idea for scaling Bitcoin.
>> As a brief introduction: I work in the payment industry and I
>> have twenty years' experience in development. I have some
>> experience with process groups and ordering protocols too. I
>> think I understand Satoshi's paper but I admit I have not read
>> the source code.
>>
>> The idea is to run more than one simultaneous chain, each chain
>> defeating double spending on only part of the coin. The coin
>> would be partitioned by radix (or modulus, not sure what to call
>> it.) For example in order to multiply throughput by a factor of
>> ten you could run ten parallel chains, one would work on coin
>> that ends in "0", one on coin that ends in "1", and so on up to "9".
>>
>> The number of chains could increase automatically over time based
>> on the moving average of transaction volume.
>>
>> Blocks would have to contain the number of the partition they
>> belong to, and miners would have to round-robin through
>> partitions so that an attacker would not have an unfair advantage
>> working on just one partition.
>>
>> I don't think there is much impact to miners, but clients would
>> have to send more than one message in order to spend money.
>> Client messages will need to enumerate coin using some sort of
>> compression, to save space. This seems okay to me since often in
>> computing client software does have to break things up in equal
>> parts (e.g. memory pages, file system blocks,) and the client
>> software could hide the details.
>>
>> Best wishes for continued success to the project.
>>
>> Regards,
>> Akiva
>>
>> P.S. I found a funny anagram for SATOSHI NAKAMOTO: "NSA IS OOOK
>> AT MATH"
>>
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev at lists.linuxfoundation.org
>> <mailto:bitcoin-dev at lists.linuxfoundation.org>
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> <mailto:bitcoin-dev at lists.linuxfoundation.org>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151208/e19fe53b/attachment.html>;
Patrick Strateman [ARCHIVE] /
npub1l3ā¦69pvv
2023-06-07 17:45:55
in reply to nevent1qā¦6szv
Author Public Key
npub1l3uf9m4yw2y7x8wyjeswhelsqyy8ql4jaca4nyy6en0s474yadssg69pvvPublished at
2023-06-07 17:45:55Event JSON
{
"id": "92726cbc0169b1178169c8477af3c2079655868af1bc6f5008fc7d0d204a905c",
"pubkey": "fc7892eea47289e31dc49660ebe7f00108707eb2ee3b59909accdf0afaa4eb61",
"created_at": 1686159955,
"kind": 1,
"tags": [
[
"e",
"1d3ba80ab0099181bba68d894affa14f996897f03fb26c19893401e942e99a33",
"",
"root"
],
[
"e",
"3dfc30f69ee4d9511b0f6d289f32ec4d9f353c5592d2927c53356e3cc5673b04",
"",
"reply"
],
[
"p",
"3609c93ca0bb4deffa85f6a8214c2f1d3f84ba90abb8964cd5175ea5b17f0c5d"
]
],
"content": "š
Original date posted:2015-12-08\nš Original message:If partition is selected from a random key (the hash of the output for\nexample) then payment recipients would need to operate a full node on\neach of the chains.\n\nWhat's the point of partitioning if virtually everybody needs to operate\neach partition?\n\nThe mining aspect has it's own set of issues, but I'm not going to get\ninto those.\n\nOn 12/08/2015 01:23 PM, Akiva Lichtner wrote:\n\u003e It's true that miners would have to be prepared to work on any\n\u003e partition. I don't see where the number affects defeating double\n\u003e spending, what matters is the nonce in the block that keeps the next\n\u003e successful miner random.\n\u003e\n\u003e I expect that the number of miners would be ten times larger as well,\n\u003e so an attacker would have no advantage working on one partition.\n\u003e\n\u003e On Tue, Dec 8, 2015 at 3:50 PM, Patrick Strateman via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\n\u003e \u003cmailto:bitcoin-dev at lists.linuxfoundation.org\u003e\u003e wrote:\n\u003e\n\u003e Payment recipients would need to operate a daemon for each chain,\n\u003e thus guaranteeing no scaling advantage.\n\u003e\n\u003e (There are other issues, but I believe that to be enough of a show\n\u003e stopper not to continue).\n\u003e\n\u003e On 12/08/2015 08:27 AM, Akiva Lichtner via bitcoin-dev wrote:\n\u003e\u003e Hello,\n\u003e\u003e\n\u003e\u003e I am seeking some expert feedback on an idea for scaling Bitcoin.\n\u003e\u003e As a brief introduction: I work in the payment industry and I\n\u003e\u003e have twenty years' experience in development. I have some\n\u003e\u003e experience with process groups and ordering protocols too. I\n\u003e\u003e think I understand Satoshi's paper but I admit I have not read\n\u003e\u003e the source code.\n\u003e\u003e\n\u003e\u003e The idea is to run more than one simultaneous chain, each chain\n\u003e\u003e defeating double spending on only part of the coin. The coin\n\u003e\u003e would be partitioned by radix (or modulus, not sure what to call\n\u003e\u003e it.) For example in order to multiply throughput by a factor of\n\u003e\u003e ten you could run ten parallel chains, one would work on coin\n\u003e\u003e that ends in \"0\", one on coin that ends in \"1\", and so on up to \"9\".\n\u003e\u003e\n\u003e\u003e The number of chains could increase automatically over time based\n\u003e\u003e on the moving average of transaction volume.\n\u003e\u003e\n\u003e\u003e Blocks would have to contain the number of the partition they\n\u003e\u003e belong to, and miners would have to round-robin through\n\u003e\u003e partitions so that an attacker would not have an unfair advantage\n\u003e\u003e working on just one partition.\n\u003e\u003e\n\u003e\u003e I don't think there is much impact to miners, but clients would\n\u003e\u003e have to send more than one message in order to spend money.\n\u003e\u003e Client messages will need to enumerate coin using some sort of\n\u003e\u003e compression, to save space. This seems okay to me since often in\n\u003e\u003e computing client software does have to break things up in equal\n\u003e\u003e parts (e.g. memory pages, file system blocks,) and the client\n\u003e\u003e software could hide the details.\n\u003e\u003e\n\u003e\u003e Best wishes for continued success to the project.\n\u003e\u003e\n\u003e\u003e Regards,\n\u003e\u003e Akiva\n\u003e\u003e\n\u003e\u003e P.S. I found a funny anagram for SATOSHI NAKAMOTO: \"NSA IS OOOK\n\u003e\u003e AT MATH\"\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e \u003cmailto:bitcoin-dev at lists.linuxfoundation.org\u003e\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003cmailto:bitcoin-dev at lists.linuxfoundation.org\u003e\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151208/e19fe53b/attachment.html\u003e",
"sig": "3c8ebfe57173960e445f2d24814e9dd2fc73a1e85116ffdd58400efaf622d7762ddc2813a7a57d1a200d99f203c3c226706ad92a4a22881073c254f980d1b53b"
}