Privacy-Enhancing Protocol Cashfusion Completes Security Analysis – Privacy Bitcoin News


Privacy-Enhancing Protocol Cashfusion Completes Security Analysis

Just a few days prior to the Bitcoin Cash anniversary, BCH fans found out that the Cashfusion audit from Kudelski Security is now complete. Electron Cash engineer Jonald Fyookball announced the audit was finished and said the protocol “passed, mostly with flying colors.”

Last February it was announced that would host a fundraiser for the Cashfusion team in order to raise $100,000. $50k worth of the money went toward an audit from the firm Kudelski Security, and the rest of the funds went toward developer expenses.

For every BCH donation sent in by the community, matched dollar for dollar. The fundraiser surpassed the goal by 103.3% or $51K worth of bitcoin cash spread out between 623 donations.

In the past, Kudelski Security also audited the Cashshuffle platform prior to its official release. After improving upon Cashshuffle with the Cashfusion protocol, developers decided to have Kudelski audit the code as well.

Privacy-Enhancing Protocol Cashfusion Completes Security Analysis

On Wednesday, Electron Cash (EC) developer Jonald Fyookball revealed that the Cashfusion audit was complete and the BCH community can read the report hosted on the EC website. Moreover, Fyookball explained that the “[Cashfusion] protocol passed, mostly with flying colors.”

“Overall, we believe that Cashfusion addresses an existing problem in managing anonymized transactions in Bitcoin Cash by adopting a reasonable security tradeoff,” the Kudelski report notes.

“We observe that the security analysis of Cashfusion considers many important aspects, although it can certainly be improved in the future. The protocol is very complex, which limits the accessibility for a sound analysis and security evaluation,” Kudelski’s findings highlight.

Kudelski Security further added that the Cashfusion codebase they reviewed “is implementing the protocol as correctly as described and we did not find any evidence of malicious intent or potential backdoor in the codebase.”

In addition to the audit, Electron Cash developer Calin Culianu announced the launch of the Electron Cash wallet version 4.1.0 with Cashfusion.

Of course, the BCH community was thrilled to hear about the completion of the security audit and Fyookball’s announcement was the top post on the Reddit forum r/btc. The top comment on the post stems from’s Roger Ver who said:

This is one of the most exciting developments of the year— Strong privacy on BCH is a big big deal.

Another BCH supporter wrote: “Love it, love it, love it— Let’s bring this puppy to wallet.

“Let’s bring it to every wallet,” another individual responded in the thread. “Users should actively opt-out and declare they will need their account/transactions to be public instead of private (standard),” he added.

Tags in this story
BCH Privacy, bitcoin cash, bitcoin cash BCH, Wallet, Calin Culianu, Cashfusion, Cashfusion codebase, Cashshuffle, Electron Cash, Jonald Fyookball, Kudelski Security, Privacy, security analysis, Security Audit

What do you think about the Cashfusion audit completion? Let us know what you think in the comments section below.

Jamie Redman

Jamie Redman is the News Lead at News and a financial tech journalist living in Florida. Redman has been an active member of the cryptocurrency community since 2011. He has a passion for Bitcoin, open-source code, and decentralized applications. Since September 2015, Redman has written more than 6,000 articles for News about the disruptive protocols emerging today.

Image Credits: Shutterstock, Pixabay, Wiki Commons, Kudelski Security, Cashfusion

Disclaimer: This article is for informational purposes only. It is not a direct offer or solicitation of an offer to buy or sell, or a recommendation or endorsement of any products, services, or companies. does not provide investment, tax, legal, or accounting advice. Neither the company nor the author is responsible, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any content, goods or services mentioned in this article.

Read disclaimer
Show comments