Search content
Sort by
Showing 8 of 8 results by LinuxDude
Thank you for the long and detailed post.
You know what? I am calling the verge team thieves. They are stealing xvgs and no one else whosoever!!!!! They can do what ocminer advised but they have closed their fucking ears. Do they have ears? I highly doubt. I didn't do enough research. But I didn't lose much money. I just only lost hope.
Fuck them. They will burn in hell with their loots.
You know what? I am calling the verge team thieves. They are stealing xvgs and no one else whosoever!!!!! They can do what ocminer advised but they have closed their fucking ears. Do they have ears? I highly doubt. I didn't do enough research. But I didn't lose much money. I just only lost hope.
Fuck them. They will burn in hell with their loots.
I understand your frustration. But calling them names or cursing them will change nothing unfortunately. What you see here might as well have nothing to do with them having closed their ears. It could be that they just plainly don't understand the code so they are incapable of providing a fix. Months ago, when I did my research on Verge looking at the source code I realised that the lead dev is at most a Junior dev that lacks the experience to provide any high quality complex code. This has been proven so many times by their "accidental" mistakes or the copy/pastes that include bugs of others.. Any rants/vents I had, went immediately away. There was no point in venting at a fish because it will not fly.. Its incapable of doing this in the first place..
Take the whole thing as a lesson. An experience to make us smarter in researching and making our choices.
Calling a dev a junior only because uses part of code from others dev makes you the junior here.
I'm a dev too and I honestly do the same to release something faster. If you understand what other devs have done in their code is legit to use it (under proper licence).
Such a person is a retard, and not a developer at all! To illustrate what has happened.
- The retard Verge dude "justinvforvendetta" used the browser !!!THE BROWSER!!! to modify the !!!MAIN BRANCH!!! !!!WITHOUT TESTING!!! !!!OF A MULTI BILLION!!! project.
- That code that the retard Verge dude changes was copy and paste, he failed to do some basic math, really really basic math.
Please do not insult junior developers, by comparing such to the verge retard.
-> My post is in general, not on what the person I quoted wrote. But in general, the verge retard with the nick justinvforvendetta shall not be called a developer, not even a junior dev.
Resorted to name calling like a child. You're pathetic. Grow up dude.
Hey guys... everything is going to be fine... consider a few things.. This is an orchestrated attack because of the pending partnership.
Rival coins want to see Verge fail so they can reign supreme. And others want the coin to tank so they can amass more volume for cheap in order to capitalize on the partnership announcement.
Everything is fine. There was an exploit. It has been discovered and a fork is coming to fix it. It's that simple.
No exit scam. No fraud. No inside job... no none of that. We're all going to be okay. Hold onto your Verge.
If you dump now because of FUD, ill-written headlines, and fall victim to exaggerated misinformation campaign, you will kick yourself come the 17th. Guaranteed. Don't fall for it. Your coins are safe. Just hold them close
Rival coins want to see Verge fail so they can reign supreme. And others want the coin to tank so they can amass more volume for cheap in order to capitalize on the partnership announcement.
Everything is fine. There was an exploit. It has been discovered and a fork is coming to fix it. It's that simple.
No exit scam. No fraud. No inside job... no none of that. We're all going to be okay. Hold onto your Verge.
If you dump now because of FUD, ill-written headlines, and fall victim to exaggerated misinformation campaign, you will kick yourself come the 17th. Guaranteed. Don't fall for it. Your coins are safe. Just hold them close
So true... These guys just want nothing more then to try to take down XVG. Pretty sad!
1)I stated fact, your account is brand new and that was your first message
2)I don't own any Verge
3)Ocminer had a very wrong behavior. You first talk to devs let sort them out a quick fix, then explain to the world what is happening. Not the "vice versa".
4)This is a drama because what happened sucks but by quoting CryptoYeff
2)I don't own any Verge
3)Ocminer had a very wrong behavior. You first talk to devs let sort them out a quick fix, then explain to the world what is happening. Not the "vice versa".
4)This is a drama because what happened sucks but by quoting CryptoYeff
Quote
at the end of the day what did we lose? 20-30 million coins--- who gives a sh!t-- means nothing compared to max supply---- we lost half a day of mining? not the end of the world.
Are really this dense or are you just pretending to be? What do you mean drama? Losing 1% of the total supply through an exploit: "no big deal".
This isn't fud you dense ***** this is truth. There is no uncertainty here, verge has a critical bug that is STILL live.
OCminder did everything exactly the way he should have done.
After contacting the dev team and getting laughed at(it is working as intended?
??)Seeing as that it's an ongoing attack his loyalty should always lie with his miners first and the devs of random coins second.
He didn't only raise public awareness without exploiting it but also mentioned solutions.
The verge dev should be getting on his goddamn knees to thank this man this man for pointing out what is happening without benefiting from it himself.
Now if we look at yesterday with the knowledge we have today what can we conclude?
1. The "fix" didn't fix it at all.
2. There was blatent lying on their twitter(not only massively underplaying the gravity of the exploit(small hash attack), it didn't just last 3 hours and they didn't fix it either).
3. The dev should be working overtime to try to fix this thing instead of barking nonsense on this site and reddit, he has his shill....marketing team for that.
4. The "fix" was copy pasted from peercoin, just as the "wraith protocol" was copy pasted from opalcoin.
This is a ridiculousness of the situation is baffling.
Justin what are you doing??? You've made so much money from this coin how is it possible that you can't hire competent coders to hotfix this and other things if you can't do it yourself???
He can't do simple math.
https://cointelegraph.com/news/cryptocurrency-verge-responds-to-hacking-claims-by-launching-accidental-hard-fork
just a catalogue of errors with this coin
this is probably one the most shilled and pumped coins on twitter, sick of seein g it at every turn
just hope the innocents get out before the whales dump their loads on them
i guess they can't even send their coins to exchange or sync wallets to dump them at this stage
socalled devs should be ashamed
just a catalogue of errors with this coin
this is probably one the most shilled and pumped coins on twitter, sick of seein g it at every turn
just hope the innocents get out before the whales dump their loads on them
i guess they can't even send their coins to exchange or sync wallets to dump them at this stage
socalled devs should be ashamed
My Wallet synced fine but that was on a fresh install w/ blockchain files from Apr3. It did get passed all blocks and sent coins from Binance to my Wallet and back just fine.
I just came here to say that the verge team is still full on trying to act like this is no big deal. They're acting like the issue is resolved on telegram and are banning anyone who point people to this thread. The exploit is being exploited right now...
Sounds to me like you're fudding to try to drive the price down.
nice a new version of the famed timewarp attack.. very interesting.
yep.. we pushed a quick fix and most pools have already updated.. we're already working on a whole new block verification process.
we're kinda glad this happened and that it wasn't as bad as it could have been.
Hmm, you guys are aware that the "fix" you pushed actually IS a hardfork ? So your blockchain snapshot is not valid anymore, the wallet's won't sync up from scratch anymore and the current chain is simply not usable anymore with that new "fix" ?
Your change simply disagrees with the attackers blocks, the first block I see from the attacker was 2007365 - so the wallets will stop syncing there and simply not progress any further.
I remember your first forking dramas when trying to fork into Tor which failed 2 times IIRC.
You should immediately refrain from that "fix" and set a proper fork-height (at least 48h) and the chain up until the fork block MUST accept blocks with the old timestamps and blocks after that fork block then only with the new timestamp.
bumping this for awareness
how can we verify the hardfork ?
just download an updated wallet which includes the "fix" - then download the blockchain snapshot and try to sync up to the latest block...it will get stuck at 2007364
Confirmed. client stalls at block 2007364
yeah we removed that, and we're doing a full fork update with extra block verifications. will be ready by tmrw =]
So are you saying the exploit can be used for the rest of the day with no repercussions?
Sounds great!
- That screams for exploit and rollback afterwards.Downloaded latest Wallet, installed blockchain files from 4/3/18 and I got past block 2007364 and it's still syncing for me.
maybe he attacks the master nodes servers and make them vote to his blocks and reject the others, then the difficulty be low and he can mining alone at near zero difficulty.
XVG doesn't use masternodes.