Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Use txid as key in mapAlreadyAskedFor #7862
Conversation
|
utACK 7e91f63 |
|
utACK 7e91f63 |
|
utACK 7e91f63 |
|
utACK 7e91f63 |
jonasschnelli
added
the
Refactoring
label
Apr 12, 2016
|
Should be tagged with "Backport 0.12.2" if this is meant for segwit. |
|
@MarcoFalke Agreed, thanks for pointing that out. |
laanwj
added
the
Needs backport
label
Apr 14, 2016
|
Makes sense to me. |
laanwj
merged commit 7e91f63
into
bitcoin:master
Apr 14, 2016
1 check passed
added a commit
that referenced
this pull request
Apr 14, 2016
added a commit
to MarcoFalke/bitcoin
that referenced
this pull request
Apr 27, 2016
|
Backported as part of #7938. Removing label 'Needs backport'. |
sdaftuar commentedApr 11, 2016
Previously we used the
CInvthat would be sent to the peer announcing the transaction as the key, but using the txid instead allows us to decouple the p2p layer from the application logic.This is a minor preparatory commit for segwit, in which the inv-type will no longer be the same for all transaction requests.