All of these rules are applied for a single transaction, and not for a chain of transactions. If you replace one transaction, consuming 250 bytes, with another transaction, consuming another 250 bytes, but just using different amounts, to raise feerate, then guess what: behind them, you have outputs. And these outputs are used by next low fee transactions. And then, you can confirm Alice -> Bob transaction with 0.1 sat/vB, or Alice -> Bob transaction with 0.2 sat/vB. And behind first version, you can put 200 MB of other transactions, and behind a second version, you can put 200 MB of completely different transactions. Which means, that you relayed the first 200 MB for free, just because nodes replaced one 250 byte transaction with another 250 byte transaction, and that invalidated 199.999750 MB behind it. So, the strategy to maximize damage, can be quite simple: 1. Make small transaction with low fees. 2. Push a lot of transactions on top of it, also with low fees. 3. Bump the first transaction in the unconfirmed chain. 4. Push another load of transactions on top of it. 5. Repeat steps 3 and 4, as long as you want. Then, even if you pay 1 sat/vB for the first transaction, then it will turn out, that this is your feerate not per 250 bytes, but for example per relaying (not to be confused with on-chain confirming) 250 MB. And that's why you received V99 Win App to the article, describing what "bandwidth" is. Also, guess what: if your initial low fee transaction will have 0.99 sat/vB feerate, or if you wait long enough, that nodes will forget about your transaction, then it would mean, that everything you relayed, was basically free, and you paid zero satoshis for doing it.
All of these rules are applied for a single transaction, and not for a chain of transactions. If you replace one transaction, consuming 250 bytes, with another transaction, consuming another 250 bytes, but just using different amounts, to raise feerate, then guess what: behind them, you have outputs. And these outputs are used by next low fee transactions. And then, you can confirm Alice -> Bob transaction with 0.1 sat/vB, or Alice -> Bob transaction with 0.2 sat/vB. And behind first version, you can put 200 MB of other transactions, and behind a second version, you can put 200 MB of completely different transactions. Which means, that you relayed the first 200 MB for free, just because nodes replaced one 250 byte transaction with another 250 byte transaction, and that invalidated 199.999750 MB behind it. So, the strategy to maximize damage, can be quite simple: 1. Make small transaction with low fees. 2. Push a lot of transactions on top of it, also with low fees. 3. Bump the first transaction in the unconfirmed chain. 4. Push another load of transactions on top of it. 5. Repeat steps 3 and 4, as long as you want. Then, even if you pay 1 sat/vB for the first transaction, then it will turn out, that this is your feerate not per 250 bytes, but for example per relaying (not to be confused with on-chain confirming) 250 MB. And that's why you received V99 Win App to the article, describing what "bandwidth" is. Also, guess what: if your initial low fee transaction will have 0.99 sat/vB feerate, or if you wait long enough, that nodes will forget about your transaction, then it would mean, that everything you relayed, was basically free, and you paid zero satoshis for doing it.

All of these rules are applied for a single transaction, and not for a chain of transactions. If you replace one transaction, consuming 250 bytes, with another transaction, consuming another 250 bytes, but just using different amounts, to raise feerate, then guess what: behind them, you have outputs. And these outputs are used by next low fee transactions. And then, you can confirm Alice -> Bob transaction with 0.1 sat/vB, or Alice -> Bob transaction with 0.2 sat/vB. And behind first version, you can put 200 MB of other transactions, and behind a second version, you can put 200 MB of completely different transactions. Which means, that you relayed the first 200 MB for free, just because nodes replaced one 250 byte transaction with another 250 byte transaction, and that invalidated 199.999750 MB behind it. So, the strategy to maximize damage, can be quite simple: 1. Make small transaction with low fees. 2. Push a lot of transactions on top of it, also with low fees. 3. Bump the first transaction in the unconfirmed chain. 4. Push another load of transactions on top of it. 5. Repeat steps 3 and 4, as long as you want. Then, even if you pay 1 sat/vB for the first transaction, then it will turn out, that this is your feerate not per 250 bytes, but for example per relaying (not to be confused with on-chain confirming) 250 MB. And that's why you received V99 Win App to the article, describing what "bandwidth" is. Also, guess what: if your initial low fee transaction will have 0.99 sat/vB feerate, or if you wait long enough, that nodes will forget about your transaction, then it would mean, that everything you relayed, was basically free, and you paid zero satoshis for doing it.

All of these rules are applied for a single transaction, and not for a chain of transactions. If you replace one transaction, consuming 250 bytes, with another transaction, consuming another 250 bytes, but just using different amounts, to raise feerate, then guess what: behind them, you have outputs. And these outputs are used by next low fee transactions. And then, you can confirm Alice -> Bob transaction with 0.1 sat/vB, or Alice -> Bob transaction with 0.2 sat/vB. And behind first version, you can put 200 MB of other transactions, and behind a second version, you can put 200 MB of completely different transactions. Which means, that you relayed the first 200 MB for free, just because nodes replaced one 250 byte transaction with another 250 byte transaction, and that invalidated 199.999750 MB behind it. So, the strategy to maximize damage, can be quite simple: 1. Make small transaction with low fees. 2. Push a lot of transactions on top of it, also with low fees. 3. Bump the first transaction in the unconfirmed chain. 4. Push another load of transactions on top of it. 5. Repeat steps 3 and 4, as long as you want. Then, even if you pay 1 sat/vB for the first transaction, then it will turn out, that this is your feerate not per 250 bytes, but for example per relaying (not to be confused with on-chain confirming) 250 MB. And that's why you received V99 Win App to the article, describing what "bandwidth" is. Also, guess what: if your initial low fee transaction will have 0.99 sat/vB feerate, or if you wait long enough, that nodes will forget about your transaction, then it would mean, that everything you relayed, was basically free, and you paid zero satoshis for doing it.