8000 transaction identity leakage during initial block download · Issue #2122 · bitcoin/bitcoin · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

transaction identity leakage during initial block download #2122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
rebroad opened this issue Dec 21, 2012 · 1 comment
Closed

transaction identity leakage during initial block download #2122

rebroad opened this issue Dec 21, 2012 · 1 comment

Comments

@rebroad
Copy link
Contributor
rebroad commented Dec 21, 2012

During initial block download ResendWalletTransactions() runs, trying to send transactions which may have already been introduced into blocks. This therefore reveals two things about the node, one that it is not up to date with the blockchain, but also that those transactions originated from this node. This information could be used by people analysing the network to determine where the transactions came from.

Can/should the code be changed to provide the option not to send wallet transactions until the block chain is more up to date?
@rebroad
Copy link
Contributor Author
rebroad commented May 12, 2013

superceded by #2445

@rebroad rebroad closed this as completed May 12, 2013
@gmaxwell gmaxwell mentioned this issue May 12, 2013
Closed
HashUnlimited pushed a commit to HashUnlimited/chaincoin that referenced this issue Jul 2, 2018
@UdjinM6
Do not create mnb until sync is finished (bitcoin#2122)
d38ad87 
We don't relay mnb if sync is still in progress. Creating mnb without
relaying it only increases inconsistency and leads to user confusion.
Unifying conditions for creation and relaying fixes this.
HashUnlimited pushed a commit to HashUnlimited/chaincoin that referenced this issue Jul 2, 2018
@UdjinM6
Do not create mnb until sync is finished (bitcoin#2122)
7e33650 
We don't relay mnb if sync is still in progress. Creating mnb without
relaying it only increases inconsistency and leads to user confusion.
Unifying conditions for creation and relaying fixes this.
HashUnlimited added a commit to chaincoin/chaincoin that referenced this issue Jul 2, 2018
@HashUnlimited
Merge pull request #26 from HashUnlimited/Hash_0.16_back
c48cce0 
Do not create mnb until sync is finished (bitcoin#2122)
HashUnlimited pushed a commit to HashUnlimited/chaincoin that referenced this issue Jul 3, 2018
@UdjinM6
Do not create mnb until sync is finished (bitcoin#2122)
2fc9233 
We don't relay mnb if sync is still in progress. Creating mnb without
relaying it only increases inconsistency and leads to user confusion.
Unifying conditions for creation and relaying fixes this.
sidhujag pushed a commit to syscoin/syscoin that referenced this issue Jul 6, 2018
@UdjinM6 @sidhujag
Do not create mnb until sync is finished (bitcoin#2122)
9a1ef49 
We don't relay mnb if sync is still in progress. Creating mnb without
relaying it only increases inconsistency and leads to user confusion.
Unifying conditions for creation and relaying fixes this.
owlhooter pushed a commit to owlhooter/mazacoin-new that referenced this issue Oct 11, 2018
@UdjinM6
Do not create mnb until sync is finished (bitcoin#2122)
b7c3261 
We don't relay mnb if sync is still in progress. Creating mnb without
relaying it only increases inconsistency and leads to user confusion.
Unifying conditions for creation and relaying fixes this.
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rebroad
0