This article was first published on vergecurrency - Medium
As far as I know it’s time for the development update again!
Verge Core’s “Roadmap”
Since we had lately released the newest version (V5.3.0) of our shiny codebase, we have seen various performance improvements and several bug fixes compared to V4.
We all know the current state of the art and what has been built on top of Verge, but we also want to keep an eye on what is actually coming in the future of Verge.
Mandatory Stealth Addressing
Yes, you heard right. In order to move forward, we’ll equip the codebase with the capabilities to send funds to stealth addresses by default. We will step-by-step clean up and require stealth addresses by default. So, whenever you generate a new address it will be a stealth-address instead of a standard address. Surely, there will still be the option to generate a standard P2SH address.
That way, stores, exchanges, etc must finally accept and use stealth-addresses by default, which would overall increase the network privacy.
Dandelion++ or Basic Ring Signatures
This topic is still up to discussion, but both are sender protecting algorithms which are making it harder for people to walk through the imaginary network graph and find the original sender of the transaction. Next to this people are already covered by the secure onion solution that is in-depth obfuscating your IP address anyways, but finding the original node is never the less a very risky situation as your node could be leaking some identifying sources (HWID etc).
So, Dandelion++ is a graph obfuscation theory which is quite new and requires a lot of pre-requirements. Shortly put it’s pure advantage is that you only need to change the way the network communicates with each other, which is way easier than integrating Ring Signatures.
Ring Signatures, on the other hand, have way fewer ...
To keep reading, please go to the original article at:
vergecurrency - Medium