My Authors
Read all threads
As an expert, dedicated team that has been pioneering and tirelessly developing a privacy centric Proof of Stake blockchain since 2016, #PIVX is extremely disappointed to see @officialmcafee @GhostbyMcAfee $ESH $GHOST blatantly plagiarizing the Sept 2018 PIVX whitepaper.
The PIVX Community has recently made us aware of John McAfee’s $GHOST project.

After a detailed investigation, it is obvious the GHOST whitepaper was plagiarized extensively from an outdated 2018 PIVX whitepaper.
Based on what McAfee and his team have published so far, we can confirm that there are many similarities between GHOST and PIVX.
Their coin specs, feature set, and protocols mentioned, all align with PIVX's specifications and the recently announced new privacy protocol (Sapling/zk-SNARKs) that is currently being implemented.
We would like to clarify that we have NO affiliation/association with the GHOST project, and have had no contact up to this point. Their current whitepaper, if implemented into a codebase, possesses several critical issues.
We found multiple instances where @officialmcafee used exactly the same wording, structure and content flow found in the 2018 PIVX whitepaper. This can be seen here (pages 2, 7 in the GHOST whitepaper)…
...and here where the $GHOST coin specs are an identical 1:1 copy (pages 8, 9 in the GHOST whitepaper)...
...and here (pages 10, 11 in the GHOST whitepaper)…
...and here (pages 11, 14 in the GHOST whitepaper)...
...and here (pages 14, 15 in the GHOST whitepaper)…
...and here (pages 16, 17 in the GHOST whitepaper)…
...and here where in this instance (page 17 in the GHOST whitepaper) @officialmcafee @GhostbyMcAfee $ESH copied and pasted the content of an instant transaction demonstration, however, forgot to remove a color key referencing a diagram that was not included.
This continues here (pages 18, 19 in the GHOST whitepaper)...
...and here (pages 19, 20 in the GHOST whitepaper)...
...and here (pages 21, 22 in the GHOST whitepaper)...
...and here (pages 22, 23, 24, 25 in the GHOST whitepaper).
We do not know what code base Ghost is forked from yet, but given the above, it is most likely PIVX. At least 20 of the 26 total pages (not including front and back covers) found in the Ghost whitepaper contain material directly plagiarized from the 2018 PIVX whitepaper.
Please note this important point: PIVX expects to complete implementation of the new Sapling /zk-SNARKs privacy protocol in Q4 2020. As such, if Ghost is indeed a fork of PIVX, it will either be waiting for PIVX to complete the privacy code or will use its own solution.
Although Ghost states it will use Sapling/zk-SNARKs, the Ghost whitepaper references obsolete Zerocoin Protocol specifications. For example, Sapling does not use any RSA-2048 accumulators and denominations as referenced by GHOST on pages 8 and 25.
As always, please DYOR and invest wisely.
Missing some Tweet in this thread? You can try to force a refresh.

Enjoying this thread?

Keep Current with PIVX

Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!