![Re: [ann][dash] dash | first anonymous coin | inventor of x11, dgw, darksend and instantx](https://ohiobitcoin.com/wp-content/uploads/2017/03/ip.bitcointalk.org "Re: [ann][dash] dash | first anonymous coin | inventor of x11, dgw, darksend and instantx")
Any word on how the Masternode Blinding is going?
next, next version. Still in the developer oven.
git blame v0.11.2.13 src/darksend.cpp | grep blind
79e50f81 (Evan Duffield 2015-03-20 08:47:19 -0700 648) //automatically downgrade for 11.2, blinding will be supported in 11.3/12.0
Is this masternode blinding explained technically anywhere?
I don’t have a link off-hand, but the gist of it is inputs are forwarded by randomly selected (by the wallet) masternodes to the currently active masternode. Therefore the active masternode can’t correlate inputs to ip addresses.
Visual depiction of Dash developer oven:
![Re: [ann][dash] dash | first anonymous coin | inventor of x11, dgw, darksend and instantx](https://ip.bitcointalk.org/?u=http%3A%2F%2Foi68.tinypic.com%2Fskzwgn.jpg&t=574&c=m9PO3Fy6xHBnUQ "Re: [ann][dash] dash | first anonymous coin | inventor of x11, dgw, darksend and instantx")
Masternode Blinding has been “in the developer oven” for nearly 3 years now.
If it’s still half-baked after so much time, perhaps Dash needs developers who are less incompetent and don’t repeatedly preannounce features that never materialize.
We’ve yet to see even a whitepaper describing Masternode blinding, much less working code.
Published at Tue, 14 Mar 2017 22:06:10 +0000
[wpr5_ebay kw=”bitcoin” num=”1″ ebcat=”” cid=”5338043562″ lang=”en-US” country=”0″ sort=”bestmatch”]{flickr|100|campaign}
