From @DrBlirpblorp:. @everyone (and especially miners), please update your node to the following version ASAP:.
25 Sep 2023, 05:32
From @DrBlirpblorp:
@everyone (and especially miners), please update your node to the following version ASAP:
During the last few hours, our network faced a *dust attack*. This attack exploits the low fees to spam the UTXO set. In the short term, a dust attack is mostly an annoyance, but in the long term it increases the storage requirements irrecoverably.
To counter the attack, Ori and myself put together a measure to greatly increase its cost (from a few cents to more than 10,000$ a day) in terms of miner fees. The fees will *not* increase for typical transactions, except in an uncommon scenario we describe below.
We stress that this is *not a fork*, blocks created by patched (resp. unpatched) nodes are still considered valid by unpatched (resp. patched) nodes. The changes are only to the transaction gossip rules and block creation rules. Consequentially, the measure effectiveness of the measure is directly proportional to the fraction of miners (in terms of hashrate) who updated their nodes. However, non mining nodes should also update to avoid propagating adversarial transactions.
The basic idea is to require that transactions charge fees if they have "excess" outputs: if a transaction has k inputs and n outputs where n>k, it must pay a fee of n-k kaspa. However, since typical transactions have one input and two outputs (due to the change address), applying this rule directly will greatly increase fees paid by ordinary users.
We avoid this by allowing transactions with at most two excess outputs that are not paying the increased fees, but *only allowing one such transaction per block*. To avoid a DoS attack where an adversary spams the network with such transactions, preventing honest transactions from being chosen, we always choose the transaction whose *latest* input is the *earliest*.
Additionally, we still want to allow mining pools to pay block rewards to many users. We achieve this by exempting transactions from the increased fees if at least one of their inputs is a coinbase UTXO.
A transaction that is currently accepted will be henceforth denied if the following three conditions hold
1. It has k inputs and n outputs, with n-k>2
2. The fee paid the transaction is less than n-k Kaspa
3. None of the inputs to the transaction are coinbase UTXOs
In particular, any application that creates transaction of this form will have to either refactor the compounding of transactions or increase the fee.
You can review the changes to the code here:
Same news in other sources
125 Sep 2023, 11:07
@everyone (and especially miners), please update your node to the following version ASAP:
The patch bumps the node version to v0.12.14 so it'll be easier to monitor and diagnose the network
P.S.: the network is under a dust transactions attack, please help us mitigate it
ORIGIN:
@everyone (and especially miners), please update your node to the following version ASAP:.
@everyone (and especially miners), please update your node to the following version ASAP: https://github.com/kaspanet/kaspad/releases/tag/anti-spam-patch7
The patch bumps the node version to v0.12.14 so it'll be easier to monitor and diagnose the network
P.S.: the network is under a dust transactions attack, please help us mitigate it
ORIGIN: https://discord.com/channels/599153230659846165/844142778232864809/1155817890860245082