Back in September when we hard forked to re-enable anonymous transactions we included an additional privacy layer to the Ghost blockchain. This additional layer, Dandelion++, was a nightmare for development to say the least. Those who have had experience implementing this protocol into their blockchain are aware of the monumental task Dandelion endures. The protocol was originally developed for Bitcoin back in 2017 (BIP156), but was never implemented. Because of this, programmers have to develop a large portion of the protocol itself to be compatible with their blockchain. This is especially true due to there being three levels of bitcoin-core being released since the inception of this protocol.
In the early stages of implementing Dandelion, ghost-core was crashing upon boot and in some cases unable to even boot. This is because the protocol works at the consensus level and executes traffic scrambling throughout the network’s nodes. Once Dandelion was able to communicate with the nodes in a manner that wouldn't crash the core, it was deemed successful and thus included in the preceding hard fork.
After further monitoring of how Dandelion was reacting in the production environment, our cryptographers determined the protocol posed a risk to the network. It was discovered that some functional tests were not processed by our lead dev at the time, which, would have exposed any complications remaining with Dandelion. Because Dandelion operates at the consensus level and the risks it posed, we were not able to simply turn off the protocol and continue with re-enabling RingCT.
With that being established, the past few months have been dedicated to temporarily removing Dandelion++ from the core, improving syncing, node propagation, and a rework for the solution to the original RingCT exploit found last March. Also included is another blockchain upgrade, Taproot. However, at the time of launch, Taproot will be disabled until a later date this year. Moving forward with anonymous transactions again, we have decided to remove Blind transactions. While we offer users the choice between public and private transactions, Blind proved to be pointless for our blockchain.
It should be stated again that Ghost was not exploited during the time before anonymous transactions were turned off, meaning the supply has not been artificially inflated by bad actors.
Existing users know that when RingCT was disabled, if you had coins in your Anon/Blind wallet, they became frozen, i.e., unable to move. With this next update users will be able to access their funds again, but will have to go through a verification process first. This is because every coin sitting in Anon/Blind has been blacklisted in order to ensure without a doubt that these coins were not artificially created. Again, this is to protect the community and the chain as a whole. In order to move these coins, users will have to create a transaction via the console and run a command that will execute this action. Funds are spendable (in exact inputs) only to a Recovery address that the elected community oversight group control through multi-sig. Once these coins have been verified legitimate, the Custodians will send these coins to the corresponding owner and they will be free to move without restriction.
For those that do not have coins frozen in Anon/Blind or do not wish to access current frozen funds, the above paragraph does not apply to you. Users will be able to create new anonymous transactions without restriction. When the update goes live, we will provide the RPC command that users must run in order to access their frozen funds. Please stay tuned for more information relating to this matter.
Source:
https://ghostbymcafee.medium.com/ghost-development-update-march-2022-46e1103ea4af
