Important thing to consider specially by those who say "this will go away".
Even if the attack were to be stopped today and the fees drop down to 1, the vulnerability that this attack is exploiting is not going to go away. Tomorrow this attack could start again or the day after tomorrow a new form of attack could exploit the same vulnerability to perform a new form of attack.
The exploit must be fixed/removed to solve this for good.
In fact the historical cases I was talking about were all the same, the attack is designed in a way that gets regular people to unknowingly participate in it. In 2015 the code name was "Stress Test", in 2023 the code name is "Ordinals".
They have tried using these vulnerabilities to perform similar attacks. In fact in early days there was an increasing number of transactions that used the outputs to store arbitrary data in the blockchain. That led to introduction of restrictions and eventually to OP_RETURN and its rules.
Ever since then we have been introducing strict rules to prevent similar attack vectors until the Taproot soft fork.
Even if the attack were to be stopped today and the fees drop down to 1, the vulnerability that this attack is exploiting is not going to go away. Tomorrow this attack could start again or the day after tomorrow a new form of attack could exploit the same vulnerability to perform a new form of attack.
The exploit must be fixed/removed to solve this for good.
About the second quoted, man i cant believe some people here saying this its not an attack on BTC, i know maybe its not a coordinate or inittially its not an attack directly against BTC, but now in an abstrac way its an attack.
Well said. It doesn't have to be some evil witches in a lair with sinister laughter being echoed while they plan their attack In fact the historical cases I was talking about were all the same, the attack is designed in a way that gets regular people to unknowingly participate in it. In 2015 the code name was "Stress Test", in 2023 the code name is "Ordinals".
The reality is that the possibility of introducing arbitrary data into the bitcoin blockchain has existed since the launch of the network, it’s just that no one has tried to widely use this possibility before.
Wrong.They have tried using these vulnerabilities to perform similar attacks. In fact in early days there was an increasing number of transactions that used the outputs to store arbitrary data in the blockchain. That led to introduction of restrictions and eventually to OP_RETURN and its rules.
Ever since then we have been introducing strict rules to prevent similar attack vectors until the Taproot soft fork.
Read the previous sentence again and try to understand that this is not a bug, but a feature.
Bitcoin is not broken and there is nothing to fix here, the system continues to work normally.
It is not a feature, it is an oversight that led to a vulnerability being introduced into a small part of the protocol which is now being exploited. That also doesn't mean the whole bitcoin is broken just because a small vulnerability was found and exploited.Bitcoin is not broken and there is nothing to fix here, the system continues to work normally.