<p>I don't think it is easily preventable but it is expensive and it would be difficult to prepare without being noticed and might be difficult to execute in a way that couldn't be detected and countered, at least partially.</p>
<p>Firstly $2.5 billion is a substantial sum to throw away unless you are a government.</p>
<p>You would initially need to buy $2.5 billion worth of Bitcoin since that is the amount you calculated you need to have available in BTC to spend in transaction fees. Large purchases of this type tend to push up the price of Bitcoin. (<a href="https://www.coindesk.com/markets/2023/01/10/poor-bitcoin-market-liquidity-keeps-crypto-whales-at-bay/" rel="nofollow noreferrer">Reference</a>).</p>
<p>Bitcoin transactions that spend $50 in fees to pay someone only some small amount such as $10 would be suspicious and could be blocked, you'd have to re-use a more significant amount, say $2000. Transactions that quickly recirculate that $2000 would also be moderately obvious and easy to block.</p>
<p>Bitcoin has survived brief periods of very high fee rates (e.g. average over $50/transaction in April 2021) - this spurred the development and adoption of higher level Bitcoin payment systems such as the Lightning Network (LN) which use the Bitcoin network relatively infrequently.</p>
<p>Bitcoin miners have invested in the future of Bitcoin and many of them might not want to assist someone evidently intending to do harm to the Bitcoin economy, even despite the short term financial gains offered. It seems likely that many would coopoerate in a defensive action once the attack was obvious. Many or almost all of the less convinced miners might have to follow along with defensive efforts to avoid being left on the wrong side of a fork. Or they would divide their effort between a lucrative fork and a fork with long term value.</p>
<p>Really the question boils down to, if you had $2500000000 and wanted to end up with $0 with the side effect of destroying Bitcoin - would there be a cheaper or quicker way? Would there be something else you could do with that money that would be more beneficial to you?</p>
<p>Ultimately this question is a bit subjective, but I guess there are some aspects of Bitcoin's operation and history that can be brought up in an answer in an objective way.</p>
<hr />
<p>Footnote re transactions per block</p>
<pre><code>blocks&gt; blockchain -file blk03359.dat -blocks -format csv
   No.,Version ,Height,Date and Time   ,   Txs,Target  ,Id
     1,2C992000,772279,2023-01-16 20:24,  3218,17077CE2,000000000000000000041832D3A631058097F4D5DF55D985E8C664EA221F317D
     2,2CDF2000,772280,2023-01-16 20:52,  3510,17077CE2,0000000000000000000116ADA2621CB8F296852A50CD022AD1A905B6D827B600
     3,20006000,772282,2023-01-16 21:16,  2788,17077CE2,0000000000000000000506A596FF3A003DB3C4E4221FA38B8A500A19A102C847
     4,27FFE000,772283,2023-01-16 21:24,  2971,17077CE2,000000000000000000045811D897C1B593F7F709E0726E88E95E3B7B7AA7C379
     5,324F0000,772284,2023-01-16 21:42,  3320,17077CE2,00000000000000000004C114CA81064110AA59C2286D5FA0BA51E02F7BF9B481
[...]
   100,20000000,772448,2023-01-17 23:17,  2787,17077CE2,000000000000000000074C2DDD69DC4266EBCE407F4CB89906D0D5A4A6C277F1
   101,20000000,772449,2023-01-17 23:20,  3012,17077CE2,00000000000000000006D59307529DE12433207000992AA7087E6560641D1503
   102,20000000,772450,2023-01-17 23:23,  1317,17077CE2,000000000000000000066B6B40258410FF5FD5C9034BC5F046FFF82CAEB5A59B
   103,293F6000,772451,2023-01-17 23:34,  2957,17077CE2,0000000000000000000427BF57B0D9DBFD00286B5F5EA6DF508ACF56D021D08F

blocks&gt; blockchain -file blk03359.dat -blocks -format csv | ^
More? perl -n -a -F&quot;,&quot; -e &quot;if (/0000/) {$t+=@F[4]; $n++;} END{print $t/$n;}&quot;
2196.54368932039
</code></pre>
<p>So, &lt;2200 tx/block on average</p>

CC BY-SA 4.0
2023-01-21T06:13:09.300Z
If there were someone with a HUGE trail of inputs spamming the chain we could identify said trail of inputs and run code that would hold off processing these inputs and prioritize transactions that don't look like spam. Comes down to the fact that obfuscating yourself on bitcoin is even more expensive than using it normally and the fact that we spend little to no time processing single transactions means if you wanted to sustain this attack it would likely end up costing way more than you would calculate it to cost. Denying incoming or outbound peers is a right held by every node.
Poseidon
CC BY-SA 4.0
2023-01-20T22:17:29.053Z
2023-01-20T22:32:54.123Z
2023-01-20T22:32:54.123Z
RedGrittyBrick
<p>A block on Bitcoin blockchain contains about 4000 transactions.</p>
<p>Since a block is added approximately every 10 minutes, in 3 months, about 51 million transactions can be added (4000 x 6 x 24 x 90 = ~51 mil)</p>
<p>A bad actor such as a government could post transactions for full capacity for 3 months with a fee of $50 per transaction (currently avg trx fee is $1.3), costing the government about $2.5 billion and causing a DOS (Denial of Service) for all other transactions (Assuming that &quot;miners&quot; prioritize transactions with higher fees).</p>
<p>Can Bitcoin network handle such an attack?</p>
<p>P.S. $50 fee is just something I made up for cost to government calculation and can be any number that is way higher than the average fee. Point is to make &quot;miners&quot; ignore all other transactions that have lower fees to cause a DOS.</p>
<p>Also, please assume that government would prepare for this scenario by first creating millions of addresses and placing some sats in them so that transactions during attack would look like legitimate transfers.</p>

CC BY-SA 4.0
2023-01-20T21:04:03.170Z
Recent blocks contain less than 2200 transactions *on average*.
RedGrittyBrick
CC BY-SA 4.0
2023-01-20T21:13:36.287Z
I went with 4000 because that is what I could find about the # of trx that can be put in a block. My question still stands for 2200 too; it would even make the attack less costly.
Nihat
CC BY-SA 4.0
2023-01-20T21:23:40.957Z
Yes, whether its 4000 or 2200 tx/block, I think someone with a spare $2500000000 to burn up could kill Bitcoin for at least a while.
RedGrittyBrick
CC BY-SA 4.0
2023-01-20T21:24:49.257Z
It is worrying. I hope to hear what bitcoin devs have to say about this.
Nihat
CC BY-SA 4.0
2023-01-20T21:34:07.567Z
First the attacker has to acquire $25 billion worth of BTC, that might push the exchange rate higher making BTC  more expensive to acquire. This might be noticed.
RedGrittyBrick
CC BY-SA 4.0
2023-01-20T21:36:36.457Z
Why? They can generate, say 1 million addresses and put about 10 dollar worth of BTC in each at a cost of 10 million USD. Then they can start the attack by submitting transactions from 1 wallet address to other.
Nihat
CC BY-SA 4.0
2023-01-20T21:39:26.283Z
They need to have enough BTC to pay the $2.5 billion you calculated they would need in fees. And that's with current low fee rates that might not stay low if April 2021 is any guide.
RedGrittyBrick
CC BY-SA 4.0
2023-01-20T21:40:45.530Z
Let us [continue this discussion in chat](https://chat.stackexchange.com/rooms/142220/discussion-between-nihat-and-redgrittybrick).
Nihat
CC BY-SA 4.0
2023-01-20T21:40:47.110Z
If it were the case that an actor was to pull off such an erroneous attack any node in the network could choose to deny including transactions sent from their ip address or even public key if they wanted to. This is similar to if you had a node on the network spamming you with anything else, like empty or invalid blocks, you could just disconnect from them. If I have this wrong someone please correct me though.
Poseidon
CC BY-SA 4.0
2023-01-20T21:43:44.877Z
@RedGrittyBrick "They need to have enough BTC to pay the $2.5 billion you calculated they would need in fees" Aah I see. I feel so stupid. Thank you! If you can add your answer below, I can set it as the answer
Nihat
CC BY-SA 4.0
2023-01-20T21:45:50.630Z
@Poseidon Attacker can use many different ip addresses and different public keys from all those generated that I mentioned. So attack would come from MANY different addresses and ips. RedGrittyBrick's explanation is satisfactory. Thank you as well
Nihat
CC BY-SA 4.0
2023-01-20T21:47:05.857Z
Even though they COULD come from many keys and address' it is incredibly unlikely and the efficiency of the transactions on the bitcoin ledger allow for this to be even more unlikely than in a situation with bloated on chain data storage. Thanks for the interesting question :) Oh not to mention that spam still looks like spam even if it is coming from multiple address' all you need to do is deny SOME of those address' and you have limited the spam greatly.
Poseidon
CC BY-SA 4.0
2023-01-20T21:48:32.767Z
@Poseidon What do you mean by efficiency of transactions? Don't miners just pick the transactions with higher fees?
Nihat
CC BY-SA 4.0
2023-01-20T21:50:04.897Z
I mean the way in which transactions are stored then processed, if it was the case that we needed to spend lots of compute time verifying transactions it would be more possible for an attacker to `spam` the chain, in a situation where verifications are quick it is actually more expensive to spam over a longer period of time.
Poseidon
CC BY-SA 4.0
2023-01-20T21:54:44.103Z
Compute time for verifying is not something I was angling at. I was just worried about legitimate looking attack transactions with higher fees that would prevent normal transactions from being processed. I got the answer for it above. Thank you
Nihat
<transaction-fees><attack><blockspace-market><spam><censorship-resistance>
Is Bitcoin fee attack preventable?
Nihat
# Is Bitcoin fee attack preventable?

(Asked by: username_0 on 2023-01-20)

A block on Bitcoin blockchain contains about 4000 transactions.

Since a block is added approximately every 10 minutes, in 3 months, about 51 million transactions can be added (4000 x 6 x 24 x 90 = ~51 mil)

A bad actor such as a government could post transactions for full capacity for 3 months with a fee of $50 per transaction (currently avg trx fee is $1.3), costing the government about $2.5 billion and causing a DOS (Denial of Service) for all other transactions (Assuming that "miners" prioritize transactions with higher fees).

Can Bitcoin network handle such an attack?

P.S. $50 fee is just something I made up for cost to government calculation and can be any number that is way higher than the average fee. Point is to make "miners" ignore all other transactions that have lower fees to cause a DOS.

Also, please assume that government would prepare for this scenario by first creating millions of addresses and placing some sats in them so that transactions during attack would look like legitimate transfers.

**Tags:** transaction-fees, attack, blockspace-market, spam, censorship-resistance

> **Comments:**
> **username_1**: Recent blocks contain less than 2200 transactions *on average*.  
> **username_0**: I went with 4000 because that is what I could find about the # of trx that can be put in a block. My question still stands for 2200 too; it would even make the attack less costly.  
> **username_1**: Yes, whether its 4000 or 2200 tx/block, I think someone with a spare $2500000000 to burn up could kill Bitcoin for at least a while.  
> **username_0**: It is worrying. I hope to hear what bitcoin devs have to say about this.  
> **username_1**: First the attacker has to acquire $25 billion worth of BTC, that might push the exchange rate higher making BTC  more expensive to acquire. This might be noticed.  
> **username_0**: Why? They can generate, say 1 million addresses and put about 10 dollar worth of BTC in each at a cost of 10 million USD. Then they can start the attack by submitting transactions from 1 wallet address to other.  
> **username_1**: They need to have enough BTC to pay the $2.5 billion you calculated they would need in fees. And that's with current low fee rates that might not stay low if April 2021 is any guide.  
> **username_0**: Let us [continue this discussion in chat](https://chat.stackexchange.com/rooms/142220/discussion-between-username_0-and-username_1).  
> **username_2**: If it were the case that an actor was to pull off such an erroneous attack any node in the network could choose to deny including transactions sent from their ip address or even public key if they wanted to. This is similar to if you had a node on the network spamming you with anything else, like empty or invalid blocks, you could just disconnect from them. If I have this wrong someone please correct me though.  
> **username_0**: @username_1 "They need to have enough BTC to pay the $2.5 billion you calculated they would need in fees" Aah I see. I feel so stupid. Thank you! If you can add your answer below, I can set it as the answer  
> **username_0**: @username_2 Attacker can use many different ip addresses and different public keys from all those generated that I mentioned. So attack would come from MANY different addresses and ips. username_1's explanation is satisfactory. Thank you as well  
> **username_2**: Even though they COULD come from many keys and address' it is incredibly unlikely and the efficiency of the transactions on the bitcoin ledger allow for this to be even more unlikely than in a situation with bloated on chain data storage. Thanks for the interesting question :) Oh not to mention that spam still looks like spam even if it is coming from multiple address' all you need to do is deny SOME of those address' and you have limited the spam greatly.  
> **username_0**: @username_2 What do you mean by efficiency of transactions? Don't miners just pick the transactions with higher fees?  
> **username_2**: I mean the way in which transactions are stored then processed, if it was the case that we needed to spend lots of compute time verifying transactions it would be more possible for an attacker to `spam` the chain, in a situation where verifications are quick it is actually more expensive to spam over a longer period of time.  
> **username_0**: Compute time for verifying is not something I was angling at. I was just worried about legitimate looking attack transactions with higher fees that would prevent normal transactions from being processed. I got the answer for it above. Thank you  

---

## 1 answers

### Answer by username_1 on 2023-01-20. Score: 3 | Accepted answer

I don't think it is easily preventable but it is expensive and it would be difficult to prepare without being noticed and might be difficult to execute in a way that couldn't be detected and countered, at least partially.

Firstly $2.5 billion is a substantial sum to throw away unless you are a government.

You would initially need to buy $2.5 billion worth of Bitcoin since that is the amount you calculated you need to have available in BTC to spend in transaction fees. Large purchases of this type tend to push up the price of Bitcoin. ([Reference](https://www.coindesk.com/markets/2023/01/10/poor-bitcoin-market-liquidity-keeps-crypto-whales-at-bay/)).

Bitcoin transactions that spend $50 in fees to pay someone only some small amount such as $10 would be suspicious and could be blocked, you'd have to re-use a more significant amount, say $2000. Transactions that quickly recirculate that $2000 would also be moderately obvious and easy to block.

Bitcoin has survived brief periods of very high fee rates (e.g. average over $50/transaction in April 2021) - this spurred the development and adoption of higher level Bitcoin payment systems such as the Lightning Network (LN) which use the Bitcoin network relatively infrequently.

Bitcoin miners have invested in the future of Bitcoin and many of them might not want to assist someone evidently intending to do harm to the Bitcoin economy, even despite the short term financial gains offered. It seems likely that many would coopoerate in a defensive action once the attack was obvious. Many or almost all of the less convinced miners might have to follow along with defensive efforts to avoid being left on the wrong side of a fork. Or they would divide their effort between a lucrative fork and a fork with long term value.

Really the question boils down to, if you had $2500000000 and wanted to end up with $0 with the side effect of destroying Bitcoin - would there be a cheaper or quicker way? Would there be something else you could do with that money that would be more beneficial to you?

Ultimately this question is a bit subjective, but I guess there are some aspects of Bitcoin's operation and history that can be brought up in an answer in an objective way.

---

Footnote re transactions per block

```
blocks> blockchain -file blk03359.dat -blocks -format csv
   No.,Version ,Height,Date and Time   ,   Txs,Target  ,Id
     1,2C992000,772279,2023-01-16 20:24,  3218,17077CE2,000000000000000000041832D3A631058097F4D5DF55D985E8C664EA221F317D
     2,2CDF2000,772280,2023-01-16 20:52,  3510,17077CE2,0000000000000000000116ADA2621CB8F296852A50CD022AD1A905B6D827B600
     3,20006000,772282,2023-01-16 21:16,  2788,17077CE2,0000000000000000000506A596FF3A003DB3C4E4221FA38B8A500A19A102C847
     4,27FFE000,772283,2023-01-16 21:24,  2971,17077CE2,000000000000000000045811D897C1B593F7F709E0726E88E95E3B7B7AA7C379
     5,324F0000,772284,2023-01-16 21:42,  3320,17077CE2,00000000000000000004C114CA81064110AA59C2286D5FA0BA51E02F7BF9B481
[...]
   100,20000000,772448,2023-01-17 23:17,  2787,17077CE2,000000000000000000074C2DDD69DC4266EBCE407F4CB89906D0D5A4A6C277F1
   101,20000000,772449,2023-01-17 23:20,  3012,17077CE2,00000000000000000006D59307529DE12433207000992AA7087E6560641D1503
   102,20000000,772450,2023-01-17 23:23,  1317,17077CE2,000000000000000000066B6B40258410FF5FD5C9034BC5F046FFF82CAEB5A59B
   103,293F6000,772451,2023-01-17 23:34,  2957,17077CE2,0000000000000000000427BF57B0D9DBFD00286B5F5EA6DF508ACF56D021D08F

blocks> blockchain -file blk03359.dat -blocks -format csv | ^
More? perl -n -a -F"," -e "if (/0000/) {$t+=@F[4]; $n++;} END{print $t/$n;}"
2196.54368932039

```

So, <2200 tx/block on average

> **Comments:**
> **username_2**: If there were someone with a HUGE trail of inputs spamming the chain we could identify said trail of inputs and run code that would hold off processing these inputs and prioritize transactions that don't look like spam. Comes down to the fact that obfuscating yourself on bitcoin is even more expensive than using it normally and the fact that we spend little to no time processing single transactions means if you wanted to sustain this attack it would likely end up costing way more than you would calculate it to cost. Denying incoming or outbound peers is a right held by every node.  

---

