/biz/ - Business & Finance

>>15227825

Wake up frens!
Zero day hackers commencing..

You seriously just want to get fucked in life.

You people need some coffee
Your stack is fucked!

wow you really don't give a shit about your stacks burning up.

KEK

so dense here

Have a (you) Pajeet

>>15229555

Hours later I finally received a private message instructing me to send an email to "fuzzbawls" and "furszy" of the PIVX organization. I thought finally, I'll be getting some answers. I was dead wrong.
In the e-mail I inquired about a PIVX address (the one I linked above) that was receiving mathematically impossible amounts of staking rewards. From then on it was radio silence. No response, no acknowledgement, no denial, absolute silence.
Things got even stranger. Shortly after, that address appears to have ceased its back-and-forth transactions momentarily, and only 2 new coins were minted since.
The timing is very suspicious, but I can not conclusively say with evidence that PIVX developers have been using their knowledge of the bug for their own benefits — let alone use it to exploit other chains. But we can not rule out the possibility.
The “fake stake” exploit clearly has not been fixed for PIVX, so the question is, was it ever fixed? Or have the attackers developed a new method in carrying out similar attacks such as this one?
However, I do believe that we are owed an explanation from the PIVX organization on their recklessness and irresponsibility in failing to alert the PoS communities, allowing these attacks to happen and go largely unnoticed.
Millions of dollars were (and are still) at stake (pun not intended) when you consider the number of projects that are running off of PIVX forks. Over 200 chains are at risk because of their lack of foresight to warn the PoS community.
These types of exploits are not the kind where you simply “wait for the next version” — it demands an immediate and swift patch. The team’s nonchalant attitude towards the bug was not only alarming, but had given me a great sense of disappointment for the PIVX team.
They have yet to respond to my emails nor reached out for a comment. This is still a developing story, inaccuracies and new information will be updated.

Why was the BitGreen devs able to halt the attack in a few days, while PIVX has knowingly let this exploit go on for god knows how long?

>>15229648

Updates as of 8/12/19 7:45 PST

I'm not sure where to even begin. The fact that the devs downright lied, started attacking me personally, banned me from their Discord after requesting a civil discussion so that I can clear their name of any wrong-doing, or being called a "nobody with a shitty chain."
I made the mistake of wandering into the PIVX discord room, and surely enough, I saw posts of not only the devs trying to discredit me, but spewing lies that contradict what they had said through their "proxy man" the other day.

>>15229668

1. The developers maintained their stance that the issue has been fixed. One problem though. That directly contradicts what I've been told the other day.

2. The developers then blamed the attacks on "crappy chains" because of their decision to comment out a line that would lead to a missing nTime check.
But wait a minute... the address that I posted which was exploiting this bug was a PIVX address? So did PIVX remove their nTime check as well?!

3. I decided to jump into the convo again, and the personal attacks began.

At this point I was banned from the channel; luckily I saw it coming and managed to get the chat logs to show the world that their mentality is still in high school drama.

4. The lack of maturity, the constant avoiding of a simple question, and the unwillingness to talk taught me a lot about "furszy." Would it have been so hard to simply explain something along the lines "X happened, but Y caused some issues, so we're working on Z."
In fact, simple human psychology studies would characterize his incredibly defensive stance as a trait of someone who is hiding something -- someone feeling extreme guilt and of whatever it may be and the fear of getting caught.

5. Was I in the wrong to be asking questions? I really wanted to clear their name of any wrong doing. This was the first email I sent to them - polite and respectful.

Something fishy is definitely going on in the fantasy world of PIVX. Lies, coverups, and silence is just scratching the surface.

>>15229704

>>15229555
btw stop projecting.

These types of exploits are not the kind where you simply “wait for the next version” — it demands an immediate and swift patch. The team’s nonchalant attitude towards the bug was not only alarming, but had given me a great sense of disappointment for the PIVX team.

Millions of dollars were (and are still) at stake (pun not intended) when you consider the number of projects that are running off of PIVX forks. Over 200 chains are at risk because of their lack of foresight to warn the PoS community.

https://www.reddit.com/r/CryptoCurrency/comments/cpnmcv/pivxs_response_to_my_last_report_its_not_pretty/?utm_source=share&utm_medium=ios_app

>>15227825
https://bitcointalk.org/index.php?topic=2827989.msg52149240#msg52149240

*Laughs in TPos with XSN*