Author: Mike Hearn 2013-08-07 21:17:41
Published on: 2013-08-07T21:17:41+00:00
The discussion is centered around the concept of 'locked inputs' in wallet implementation. The issue arises when constructing a transaction but not broadcasting it right away, as the inputs must be locked to avoid accidental double-spending. Bitcoinj separates the idea of committing a transaction to the wallet from broadcasting it, however, transactions that haven't been seen in the chain yet will still be announced when a new peer is connected. It would require additional code to suppress this feature, and its usefulness is not clear. There is agreement that it should be the merchant's responsibility to get the transaction out there, but having the client do the broadcast as well can't really hurt, except perhaps for some privacy impact.
Updated on: 2023-06-07T14:55:28.093092+00:00