Raystonn . [ARCHIVE] on Nostr: ๐
Original date posted:2015-06-08 ๐ Original message:> There will always be a ...
๐
Original date posted:2015-06-08
๐ Original message:> There will always be a blocksize limit based on technological
> considerations - the network has a finite bandwidth limit.
A bandwidth limit is not the same as a blocksize limit. Bandwidth is unique
to every individual. Miners in China have different bandwidth and
connectivity than miners in the U.S., for example. But the block size limit
is dictated for eveyone. They are not comparable.
> Without a blocksize limit the attacker would just flood the network until
> the bandwidth usage became so great that consensus would fail, rendering
> Bitcoin both worthless, and insecure.
No, with no blocksize limit, a spammer would would flood the network with
transactions until they ran out of money. Meanwhile, everyone would jump on
board trying to mine the blocks to collect the fees from the spammers. It
could be one of the greatest transfers of wealth ever. Bitcoin
infrastructure would build up to handle the required bandwidth, paid for by
the very entity spamming the network. Bitcoin would flourish, growing
wildly as long as the fees kept coming. This is antifragility at its best.
> The worst an attacker flooding the network with transactions with a
> blocksize limit can do is raise costs, without harming security.
No, at attacker flooding the network with transactions with a blocksize
limit can keep their fees high enough that perhaps 1% of transactions coming
from real end-users go through. At this point everyone would give up on
Bitcoin as it would become completely unusable. The BTCUSD market would
tank, making it even easier to pay the transaction fees to keep real
transactions out of blocks, as it would continue to become cheaper and
eventually cost-free to obtain the bitcoin fees through market purchase.
-----Original Message-----
From: Peter Todd
Sent: Monday, June 08, 2015 2:44 PM
To: Raystonn .
Cc: Patrick Mccorry (PGR) ; Bitcoin Dev
Subject: Re: [Bitcoin-development] New attack identified and potential
solution described: Dropped-transaction spam attack against the blocksize
limit
On Mon, Jun 08, 2015 at 02:33:54PM -0700, Raystonn . wrote:
> > the attack would be expensive.
>
> For attacks being waged to destroy Bitcoin by filling all blocks with spam
> transactions, the attack succeeds when the attacker is well funded. This
> gives well-funded private and/or public entities the means to destroy
> Bitcoin if they desire. This is only true after the block size limit was
> implemented. Without the block size limit, the spam doesnโt harm Bitcoin.
> It simply enriches miners at the cost of the spammers, which is a nicely
> antifragile quality.
There will always be a blocksize limit based on technological
considerations - the network has a finite bandwidth limit.
Without a blocksize limit the attacker would just flood the network until
the bandwidth usage became so great that consensus would fail, rendering
Bitcoin both worthless, and insecure.
The worst an attacker flooding the network with transactions with a
blocksize limit can do is raise costs, without harming security. Keep in
mind, that at some point it'd be cheaper to just 51% attack the network.
Based on the current block subsidy of 25BTC/MB that's at the point where
transaction fees are 25mBTC/KB, which corresponds to <$2/tx fees - not that
cheap, but still quite affordable for a large percentage of Bitcoin's users
right now. And that's the *absolute worst-case* attack possible.
Published at
2023-06-07 15:37:08Event JSON
{
"id": "d97ade29873f4b08b21c93a7b76073d07cabb887967757982fcbef0788635e85",
"pubkey": "3e6baaf01f15cb9383746ee7c1a225175502acbc3234f3e42160ad71d011e092",
"created_at": 1686152228,
"kind": 1,
"tags": [
[
"e",
"bb822df33a2311a9ca89d4569d257edafe783786283eeb6a07e4d92a36b392d7",
"",
"root"
],
[
"e",
"46b8ac5e0d95f9ca45c471521148c04ed660aa819d68d29e04a33d42bbb15466",
"",
"reply"
],
[
"p",
"3e6baaf01f15cb9383746ee7c1a225175502acbc3234f3e42160ad71d011e092"
]
],
"content": "๐
Original date posted:2015-06-08\n๐ Original message:\u003e There will always be a blocksize limit based on technological \n\u003e considerations - the network has a finite bandwidth limit.\n\nA bandwidth limit is not the same as a blocksize limit. Bandwidth is unique \nto every individual. Miners in China have different bandwidth and \nconnectivity than miners in the U.S., for example. But the block size limit \nis dictated for eveyone. They are not comparable.\n\n\u003e Without a blocksize limit the attacker would just flood the network until \n\u003e the bandwidth usage became so great that consensus would fail, rendering \n\u003e Bitcoin both worthless, and insecure.\n\nNo, with no blocksize limit, a spammer would would flood the network with \ntransactions until they ran out of money. Meanwhile, everyone would jump on \nboard trying to mine the blocks to collect the fees from the spammers. It \ncould be one of the greatest transfers of wealth ever. Bitcoin \ninfrastructure would build up to handle the required bandwidth, paid for by \nthe very entity spamming the network. Bitcoin would flourish, growing \nwildly as long as the fees kept coming. This is antifragility at its best.\n\n\u003e The worst an attacker flooding the network with transactions with a \n\u003e blocksize limit can do is raise costs, without harming security.\n\nNo, at attacker flooding the network with transactions with a blocksize \nlimit can keep their fees high enough that perhaps 1% of transactions coming \nfrom real end-users go through. At this point everyone would give up on \nBitcoin as it would become completely unusable. The BTCUSD market would \ntank, making it even easier to pay the transaction fees to keep real \ntransactions out of blocks, as it would continue to become cheaper and \neventually cost-free to obtain the bitcoin fees through market purchase.\n\n\n-----Original Message----- \nFrom: Peter Todd\nSent: Monday, June 08, 2015 2:44 PM\nTo: Raystonn .\nCc: Patrick Mccorry (PGR) ; Bitcoin Dev\nSubject: Re: [Bitcoin-development] New attack identified and potential \nsolution described: Dropped-transaction spam attack against the blocksize \nlimit\n\nOn Mon, Jun 08, 2015 at 02:33:54PM -0700, Raystonn . wrote:\n\u003e \u003e the attack would be expensive.\n\u003e\n\u003e For attacks being waged to destroy Bitcoin by filling all blocks with spam \n\u003e transactions, the attack succeeds when the attacker is well funded. This \n\u003e gives well-funded private and/or public entities the means to destroy \n\u003e Bitcoin if they desire. This is only true after the block size limit was \n\u003e implemented. Without the block size limit, the spam doesnโt harm Bitcoin. \n\u003e It simply enriches miners at the cost of the spammers, which is a nicely \n\u003e antifragile quality.\n\nThere will always be a blocksize limit based on technological \nconsiderations - the network has a finite bandwidth limit.\n\nWithout a blocksize limit the attacker would just flood the network until \nthe bandwidth usage became so great that consensus would fail, rendering \nBitcoin both worthless, and insecure.\n\nThe worst an attacker flooding the network with transactions with a \nblocksize limit can do is raise costs, without harming security. Keep in \nmind, that at some point it'd be cheaper to just 51% attack the network. \nBased on the current block subsidy of 25BTC/MB that's at the point where \ntransaction fees are 25mBTC/KB, which corresponds to \u003c$2/tx fees - not that \ncheap, but still quite affordable for a large percentage of Bitcoin's users \nright now. And that's the *absolute worst-case* attack possible.",
"sig": "f46ff7967b193480f54cb7788738be5dba6f9277c68164201aff05d2ec7055c6b7ad1ea795d407e86b2ed470669bf0d569a8d2011ffe4c73da63ac99cfdf150d"
}