-
Notifications
You must be signed in to change notification settings - Fork 1
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
Is the work on Dandelion on hold? #17
Comments
Yes--we've been trying to sort out some theoretical questions that will impact our implementation decisions. This is taking a bit longer than expected, but we are actively working on it and will resume working on the implementation soon. |
Thank you. Based on my experience this would take years to be added to Core. I am working on three Bitcoin wallets (HiddenWallet, BreezeWallet, C# Bitcoin full node) and if private transaction broadcasting would be solved we could wipe out Tor dependency. I am thinking about setting up an internal peer to peer network within our nodes (full nodes and full blockspv nodes (note: full block spv nodes don't keep mempool, nor blocks so cannot check a bunch of things, but they get all blocks and all mempool transactions)) implementing and deploying a temporary pre-alpha Dandelion within such internal p2p network until it gets into Bitcoin core. I'd like to hear if you have some thoughts on this. |
Sure, you're obviously welcome to implement a pre-alpha-version of Dandelion among the full and full blockspvnodes, and we would be happy to advise if you have any questions. You should be aware that Dandelion doesn't give individual protections for nodes who are worried about eclipse attacks--this is meant to prevent large-scale monitoring. So nodes may still want to use Tor if they are worried about being individually targeted. |
I am very interested in seeing this or a similar technology implemented into Bitcoin. Are you guys still actively working on it?
The text was updated successfully, but these errors were encountered: