Who are the bitcoin core developers2/28/2023 A dust attack happens when an attacker sends a tiny amount of BTC to a number of different addresses and observes various wallets’ rebroadcasting behaviors, thus undermining the network’s privacy feature. “This leaves room for a vulnerability called a dust attack,” she argued. As a result, if a spy node sees two INV messages for the same transaction coming from a node, it can infer that the node is the source wallet, “making privacy a dead giveaway.” With the current system, she said, only the source wallet will rebroadcast transactions. “The current rebroadcast logic is terrible for privacy,” Uttarwar said, explaining her motivation for the proposed change. If such issues arise, users would have to send out another INV message and rebroadcast it to their peers. For example, there could be issues with relay or the transaction could get evicted from the mempool when other transactions have higher fee rates. However, the initial broadcast does not always go through. 2019 presentation, they need to broadcast the transaction – meaning they must send out an INV message to their peers and make sure that the transaction is in other people’s memory pool, or mempool. When users initiate a bitcoin transaction, as Uttarwar explained at a Sep. Her main focus right now concerns a proposed change to bitcoin's rebroadcast logic, which Pieter Wuille previously highlighted as one of a number of promising peer-to-peer implementation projects. Bitcoin Core developer Amiti Uttarwar is working on revising the network’s rebroadcast logic to introduce more privacy into the transaction rebroadcasting process.Ī relatively new addition to the Bitcoin Core team, Uttarwar was first employed as a Bitcoin Core developer at crypto startup Xapo in Oct.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |