Author: shymaa arafat 2021-10-08 07:44:59
Published on: 2021-10-08T07:44:59+00:00
In a discussion about making all dust transactions invalid by some nodes, a compromise was suggested to keep them in secondary storage for full nodes and in a separate Merkle Tree for bridge servers. This solution would enhance performance on bridge servers and, since dust transactions usually appear in clusters, they would be fetched rarely on full nodes. The suggestion is that uploading the whole dust partition if they were called more than a certain threshold, say more than one transaction in a block, would avoid DoS attacks. The dust would then be kept there for a while as a separate partition to exclude them from any caching mechanism after that block. The "while" could be a tuned parameter. The proposal would help decrease the amount of dust in the UTXO set. In response to concerns about worst-case behavior, it was noted that attackers would use all transactions in a block to create the worst-case scenario.
Updated on: 2023-06-15T00:47:25.788852+00:00