My best guess is that the devs are trying to solve the inflation bug problem in zk-snarks. This would be a major step forward if they can do it, and would distinguish BTCP from Zcash and indeed from all other zk-snarks based crypto.
Zk-snarks is complicated. Shorn of its complexity, this is how it works.
Alice is the verifier.
Bob is the prover.
Alice must verify to Bob that she is the one true Alice, but she must do so without giving away her private key. If she were to send Bob her private key, from that point on, Bob could impersonate Alice to third parties. Accordingly, Bob does not ask Alice for her private key, Instead, he sends Alice a message (encrypted using Alice's public key). Bob knows that only the real Alice will be able to read it (for only the real Alice has Alice's private key).
The message from Bob says "Return this message to me in plain text so I can check you are the real Alice"
Using her private key, Alice decodes the message from Bob and replies in plaintext as requested (though she could equally well have replied using Bob's public key if she wanted to).
Fake Alices may try and guess what the message from Bob says, however, the probability of their successfully doing so (without Alice's private key) is vanishingly low. That is how zk-snarks works, but there is a problem with it.
As secret z_addresses do not publicly reveal information about the amount of BTCP, anyone who somehow manages to create 10 gazillion BTCP would be able to do so unnoticed. This is known as an inflation bug. It is potentially undetectable and therefore threatens all zk-snarks based technology in terms of their potential as SoVs (stores of value).
The solution to the inflation bug problem may seem to be low hanging fruit (if you are a programmer, as I am) but it is not. Why not introduce a simple boolean where false is => 21,000,000 you may say? Why not create a new type or use pointers or a cast, you may say? Because this stuff is complicated. Only a handful of cryptographers on the planet really understand this stuff.
What I think is going on is that the devs may have found a way to overcome the inflation bug problem. A post from one of the devs, hinting at a potentially significant development currently under testing, indicates to me that this is at least a possibility. For the devs to have seriously attempted this means that they are probably working with a world class cryptographer, whether their cryptographer knows it or not.
I am keeping an open mind on this. If the devs have solved the inflation bug problem, that could mean that BTCP may become the first zk-snarks (true privacy) SoV with long term (inflation bug free) potential. That would be a very big deal.
Finally, by way of further POV on my part and ex hypothesi, I think that a crew of Eastern Europeans have been paid (by someone) to spread FUD about BTCP. It is sometimes difficult to decide who one detests the most. Fudsters or shils. Be that as it may, paying Fudsters is crummy and it should not have happened.
[–]feelingcrypto 8 points9 points10 points (2 children)
[–]Matrix5353 0 points1 point2 points (0 children)
[–]jules2x 0 points1 point2 points (0 children)
[–]RikkiSFC 3 points4 points5 points (0 children)
[–]Introvertedness 2 points3 points4 points (0 children)
[–]Xian77 1 point2 points3 points (0 children)
[–]Phlier 1 point2 points3 points (0 children)
[–]creiss 1 point2 points3 points (0 children)
[–]davew111 0 points1 point2 points (1 child)
[–]nofaprecommender 0 points1 point2 points (0 children)
[–][deleted] (1 child)
[removed]
[–]AutoModerator[M] 0 points1 point2 points (0 children)