Skip to content
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.

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

Possible way for a supernode to learn the stem #15

Open
amiller opened this issue Jun 18, 2017 · 0 comments
Open

Possible way for a supernode to learn the stem #15

amiller opened this issue Jun 18, 2017 · 0 comments
Labels

Comments

@amiller
Copy link
Collaborator

amiller commented Jun 18, 2017

As of 66d0cf2, if a node receives an DINV(tx) corresponding to a tx already under embargo, then embargo ends immediately and the transaction is propagated like usual in "fluff" mode. This is intended to help handle "cycles" gracefully without the transaction getting stuck.

However, this leads to a possible strategy for a supernode to identify the nodes involved in a stem. Upon receiving a stem message DTX(tx), the attacker could send DTX(tx) to every node. For nodes that already have the stem, this would certainly cause them to "fluff" immediately; for nodes that don't, they would fluff with only 0.1 probability.

A mitigation would be to handle cycles a different way... enter fluff mode upon receiving a DINV from the same peer a second time. This would require storing some additional data somewhere (right now we forget who told us about the tx).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant