thats a good thing
Topic: [$XVG] VERGE [POW][MultiAlgo][TOR/i2P][no premine/ico!] - page 125. (Read 843777 times)
see... someone else posted the same link to the twitter ..thing.
thats a good thing
thats a good thing
Twitter announcements
We had a small hash attack that lasted about 3 hours earlier this morning, it's been cleared up now. We will be implementing even more redundancy checks for things of this nature in the future!
https://twitter.com/vergecurrency/status/981578693062610950
We had a small hash attack that lasted about 3 hours earlier this morning, it's been cleared up now. We will be implementing even more redundancy checks for things of this nature in the future!
https://twitter.com/vergecurrency/status/981578693062610950
to prevent more fake news:
(sumup of tweet)
We had a small hash attack that lasted about 3 hours earlier this morning, it's been cleared up now. We will be implementing even more redundancy checks for things of this nature in the future!
https://twitter.com/vergecurrency/status/981578693062610950?s=19
(sumup of tweet)
We had a small hash attack that lasted about 3 hours earlier this morning, it's been cleared up now. We will be implementing even more redundancy checks for things of this nature in the future!
https://twitter.com/vergecurrency/status/981578693062610950?s=19
More fake news? Are you implying this was fake news? What a joke.
Someone presents a major flaw in your code that led to an attack, in fact presents irrevocable evidence in a sound and thoughtful manner and you throw out the term fake news? Please explain what portion of this is fake news...
not sure what your implying that im implying. I just posted facts so there is no fake news posted. keep up.
to prevent more fake news:
(sumup of tweet)
We had a small hash attack that lasted about 3 hours earlier this morning, it's been cleared up now. We will be implementing even more redundancy checks for things of this nature in the future!
https://twitter.com/vergecurrency/status/981578693062610950?s=19
(sumup of tweet)
We had a small hash attack that lasted about 3 hours earlier this morning, it's been cleared up now. We will be implementing even more redundancy checks for things of this nature in the future!
https://twitter.com/vergecurrency/status/981578693062610950?s=19
More fake news? Are you implying this was fake news? What a joke.
Someone presents a major flaw in your code that led to an attack, in fact presents irrevocable evidence in a sound and thoughtful manner and you throw out the term fake news? Please explain what portion of this is fake news...
to prevent more fake news:
(sumup of tweet)
We had a small hash attack that lasted about 3 hours earlier this morning, it's been cleared up now. We will be implementing even more redundancy checks for things of this nature in the future!
https://twitter.com/vergecurrency/status/981578693062610950?s=19
(sumup of tweet)
We had a small hash attack that lasted about 3 hours earlier this morning, it's been cleared up now. We will be implementing even more redundancy checks for things of this nature in the future!
https://twitter.com/vergecurrency/status/981578693062610950?s=19
how many coins hackers mined total ?
In the neighborhood of ~363k. Minor compared to the total float (~0.0025%), but the significance is that this happened at all.
how many coins hackers mined total ?
dev team actually already working on a fix.
(and i think finished already)
3 hrs of some orphans i think it was. not sure exactly.
some say 3, others more. dont know exactly how long.
and several pools are already up and mining again.
diff was low for a bit, now heading up again.
(and i think finished already)
3 hrs of some orphans i think it was. not sure exactly.
some say 3, others more. dont know exactly how long.
and several pools are already up and mining again.
diff was low for a bit, now heading up again.
Thank you disabled at zergpool.com too
Welcome!
new VERGE pool on poolovich.pro
http://poolovich.pro/images/poolovich.iMlG0.png
http://poolovich.pro
https://discord.gg/SKpRsbR
Low fee 0.5%, dedicated powerfull server, Super stable connection.
Baikal's owners and others are welcome.
DDoS Protection
http://poolovich.pro/images/poolovich.iMlG0.png
http://poolovich.pro
Code:
-a myr-gr -o stratum+tcp://pool.poolovich.pro:5034 -u YOUR_WALLET -p c=XVG
https://discord.gg/SKpRsbR
Low fee 0.5%, dedicated powerfull server, Super stable connection.
Baikal's owners and others are welcome.
DDoS Protection
What a pump in price for Verge. Congrats guys. I don't know about what's happening with the mining pool though.
There's currently a >51% attack going on on XVG which exploits a bug in retargeting in the XVG code.
Usually to successfully mine XVG blocks, every "next" block must be of a different algo.. so for example scrypt,then x17, then lyra etc.
Due to several bugs in the XVG code, you can exploit this feature by mining blocks with a spoofed timestamp. When you submit a mined block (as a malicious miner or pool) you simply
set a false timestamp to this block one hour ago and XVG will then "think" the last block mined on that algo was one hour ago.. Your next block, the subsequent block
will then have the correct time.. And since it's already an hour ago (at least that is what the network thinks) it will allow this block to be added to the main chain as well.
This is what is going on since about 06:00 UTC of 04.04.2018:
As you can see in the text above, those blocks are all subsequent, so one miner gets them all and you see there's 90 min difference between all the blocks, thats one bug the miner is
exploiting. You also see the correct time is the latter time.. so the last block ended on 13:51:06 and the block before was 12:17:47 and the block with the correct time before that one
was at 13:51:05 .. That means the hacker is mining one block per second !
The vergeDEV @ Discord says "everything is okay - there's nothing to fix"..
Since about 99% blocks by legit pools are rejected - and the dev team is not able to understand this problem, i'm closing and removing all VERGE pools from suprnova.
Usually to successfully mine XVG blocks, every "next" block must be of a different algo.. so for example scrypt,then x17, then lyra etc.
Due to several bugs in the XVG code, you can exploit this feature by mining blocks with a spoofed timestamp. When you submit a mined block (as a malicious miner or pool) you simply
set a false timestamp to this block one hour ago and XVG will then "think" the last block mined on that algo was one hour ago.. Your next block, the subsequent block
will then have the correct time.. And since it's already an hour ago (at least that is what the network thinks) it will allow this block to be added to the main chain as well.
This is what is going on since about 06:00 UTC of 04.04.2018:
Code:
SetBestChain: new best=00000000049c2d3329a3 height=2009406 trust=2009407 date=04/04/18 13:50:09
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000a307b54dfcf height=2009407 trust=2009408 date=04/04/18 12:16:51
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000196f03f5727e height=2009408 trust=2009409 date=04/04/18 13:50:10
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000010b42973b6ec height=2009409 trust=2009410 date=04/04/18 12:16:52
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000e0655294c73 height=2009410 trust=2009411 date=04/04/18 12:16:53
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000013490372b825 height=2009411 trust=2009412 date=04/04/18 12:16:54
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000017192ea8924b height=2009412 trust=2009413 date=04/04/18 13:50:13
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000007f75f237b3b height=2009413 trust=2009414 date=04/04/18 12:16:55
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000006ecb5753261 height=2009414 trust=2009415 date=04/04/18 13:50:14
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000019eb5bfd2f76 height=2009415 trust=2009416 date=04/04/18 12:16:56
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000018d5b80c0ee9 height=2009416 trust=2009417 date=04/04/18 13:50:15
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000159ca0701894 height=2009417 trust=2009418 date=04/04/18 12:16:57
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000ad1a8cd6b44 height=2009418 trust=2009419 date=04/04/18 13:50:16
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001002986218fc height=2009419 trust=2009420 date=04/04/18 12:16:58
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000b58e4fed470 height=2009420 trust=2009421 date=04/04/18 13:50:17
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000d9f0707d83f height=2009421 trust=2009422 date=04/04/18 12:16:59
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000007283d98dbb0 height=2009422 trust=2009423 date=04/04/18 12:17:00
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000002ec7b8a6e80 height=2009423 trust=2009424 date=04/04/18 12:17:01
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001f359a8f2f4a height=2009424 trust=2009425 date=04/04/18 13:50:20
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000293a6723940 height=2009425 trust=2009426 date=04/04/18 12:17:02
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001397927ec69d height=2009426 trust=2009427 date=04/04/18 13:50:21
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000efb6e062c02 height=2009427 trust=2009428 date=04/04/18 12:17:03
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001e181a0d0f4a height=2009428 trust=2009429 date=04/04/18 13:50:22
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000008ca5848691b height=2009429 trust=2009430 date=04/04/18 12:17:04
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000066a216ac27b height=2009430 trust=2009431 date=04/04/18 13:50:23
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001874a45f28c7 height=2009431 trust=2009432 date=04/04/18 12:17:05
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000005bc0408b8ca height=2009432 trust=2009433 date=04/04/18 13:50:24
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000005feb2b45e5d height=2009433 trust=2009434 date=04/04/18 12:17:06
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000000c211ba04de height=2009434 trust=2009435 date=04/04/18 12:17:07
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001402dc20ae5f height=2009435 trust=2009436 date=04/04/18 12:17:08
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001e73181cf91c height=2009436 trust=2009437 date=04/04/18 13:50:27
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000062720b222ea height=2009437 trust=2009438 date=04/04/18 12:17:09
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000e10aeecf7f1 height=2009438 trust=2009439 date=04/04/18 13:50:28
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000b41ab258a8f height=2009439 trust=2009440 date=04/04/18 12:17:10
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001136b924f67b height=2009440 trust=2009441 date=04/04/18 13:50:29
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000a1c1af529cd height=2009441 trust=2009442 date=04/04/18 12:17:11
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000007f1d1f8d921 height=2009442 trust=2009443 date=04/04/18 13:50:30
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000ca0a1bc6b0e height=2009443 trust=2009444 date=04/04/18 12:17:12
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000003075b7a580 height=2009444 trust=2009445 date=04/04/18 13:50:31
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001c9f43fd7305 height=2009445 trust=2009446 date=04/04/18 12:17:13
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000009129b024a height=2009446 trust=2009447 date=04/04/18 12:17:14
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000008e180f24f15 height=2009447 trust=2009448 date=04/04/18 12:17:15
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000084eb6c59c6d height=2009448 trust=2009449 date=04/04/18 13:50:34
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000d8510f41c9a height=2009449 trust=2009450 date=04/04/18 12:17:16
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000011df91a1ab87 height=2009450 trust=2009451 date=04/04/18 13:50:35
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001ba92e976854 height=2009451 trust=2009452 date=04/04/18 12:17:17
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000364bf981384 height=2009452 trust=2009453 date=04/04/18 13:50:36
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000012d88fa3db27 height=2009453 trust=2009454 date=04/04/18 12:17:18
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000305cd62b1f2 height=2009454 trust=2009455 date=04/04/18 13:50:37
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000011300c4f86cb height=2009455 trust=2009456 date=04/04/18 12:17:19
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000001487b026dd4 height=2009456 trust=2009457 date=04/04/18 13:50:38
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000001c8532ef2df height=2009457 trust=2009458 date=04/04/18 12:17:20
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001c17ae6efeeb height=2009458 trust=2009459 date=04/04/18 12:17:21
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000002bf168f5eab height=2009459 trust=2009460 date=04/04/18 12:17:22
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001a23e2c283bc height=2009460 trust=2009461 date=04/04/18 13:50:41
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000014ecd97066c4 height=2009461 trust=2009462 date=04/04/18 12:17:23
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001643a1c4a3bb height=2009462 trust=2009463 date=04/04/18 13:50:42
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000008ec0214e6c2 height=2009463 trust=2009464 date=04/04/18 12:17:24
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000009b069fcd1cc height=2009464 trust=2009465 date=04/04/18 13:50:43
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001722adbca417 height=2009465 trust=2009466 date=04/04/18 12:17:25
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000a9e8d58c86b height=2009466 trust=2009467 date=04/04/18 13:50:44
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000010f27ab0a452 height=2009467 trust=2009468 date=04/04/18 12:17:26
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000479c982db76 height=2009468 trust=2009469 date=04/04/18 13:50:45
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001f8be1b4066c height=2009469 trust=2009470 date=04/04/18 12:17:27
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000b05233d5ad7 height=2009470 trust=2009471 date=04/04/18 12:17:28
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000007a9c6cdba5d height=2009471 trust=2009472 date=04/04/18 12:17:29
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000622e29e4307 height=2009472 trust=2009473 date=04/04/18 13:50:48
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001a8d80324a57 height=2009473 trust=2009474 date=04/04/18 12:17:30
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001eddc0154526 height=2009474 trust=2009475 date=04/04/18 13:50:49
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000ac0a256f263 height=2009475 trust=2009476 date=04/04/18 12:17:31
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000040f83b5ee2f height=2009476 trust=2009477 date=04/04/18 13:50:50
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001827966aa60b height=2009477 trust=2009478 date=04/04/18 12:17:32
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000012d0d1501121 height=2009478 trust=2009479 date=04/04/18 13:50:51
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000032868a4c74 height=2009479 trust=2009480 date=04/04/18 12:17:33
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000092675395f6e height=2009480 trust=2009481 date=04/04/18 13:50:52
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001f95a9a174d4 height=2009481 trust=2009482 date=04/04/18 12:17:34
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000017503fc3dc13 height=2009482 trust=2009483 date=04/04/18 12:17:35
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000007c61b36c76 height=2009483 trust=2009484 date=04/04/18 12:17:36
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000070810d5a6e5 height=2009484 trust=2009485 date=04/04/18 13:50:55
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000068467683637 height=2009485 trust=2009486 date=04/04/18 12:17:37
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000041dc83f0978 height=2009486 trust=2009487 date=04/04/18 13:50:56
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000011fb17203f4 height=2009487 trust=2009488 date=04/04/18 12:17:38
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000a96b38de1a0 height=2009488 trust=2009489 date=04/04/18 13:50:57
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000121e7a285719 height=2009489 trust=2009490 date=04/04/18 12:17:39
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000348e668204f height=2009490 trust=2009491 date=04/04/18 13:50:58
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000012766d85cab4 height=2009491 trust=2009492 date=04/04/18 12:17:40
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000181a0c1be275 height=2009492 trust=2009493 date=04/04/18 13:50:59
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000015c05593e210 height=2009493 trust=2009494 date=04/04/18 12:17:41
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000719cb24d9c0 height=2009494 trust=2009495 date=04/04/18 12:17:42
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000015d9b853834d height=2009495 trust=2009496 date=04/04/18 12:17:43
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000115e68a6d447 height=2009496 trust=2009497 date=04/04/18 13:51:02
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000004d9233f19c6 height=2009497 trust=2009498 date=04/04/18 12:17:44
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000141ab049fe19 height=2009498 trust=2009499 date=04/04/18 13:51:03
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001b91344fa33c height=2009499 trust=2009500 date=04/04/18 12:17:45
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000001d112440f7b height=2009500 trust=2009501 date=04/04/18 13:51:04
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001bf2c8a073c6 height=2009501 trust=2009502 date=04/04/18 12:17:46
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000116863c0157c height=2009502 trust=2009503 date=04/04/18 13:51:05
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000ec5da17852e height=2009503 trust=2009504 date=04/04/18 12:17:47
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000d7cd87c5e53 height=2009504 trust=2009505 date=04/04/18 13:51:06
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000156becbf42cd height=2009505 trust=2009506 date=04/04/18 12:17:48
ProcessBlock: ACCEPTED (scrypt)
As you can see in the text above, those blocks are all subsequent, so one miner gets them all and you see there's 90 min difference between all the blocks, thats one bug the miner is
exploiting. You also see the correct time is the latter time.. so the last block ended on 13:51:06 and the block before was 12:17:47 and the block with the correct time before that one
was at 13:51:05 .. That means the hacker is mining one block per second !
The vergeDEV @ Discord says "everything is okay - there's nothing to fix"..
Since about 99% blocks by legit pools are rejected - and the dev team is not able to understand this problem, i'm closing and removing all VERGE pools from suprnova.
I have seen lots of chart evaluation that states even in 12cents perXVG that like a long term investment decision this should pay out
Hello Verge team.
Thank you for taking the scammers C-CEX from your website! Thank you! I hope I was the last of these used!
I would like to donate as well.
But all my liquidity has disappeared on C-CEX at the scam in XVG!
greetings
So sorry, and thanks!
Hallo Verge-Team.
Danke das ihr die Betrüger C-CEX von eurer Website genommen habt! Danke! Ich hoffe ich war der letzte der diesen nutzte!
Ich würde gerne auch spenden.
Aber meine ganze Liquidität ist auf C-CEX bei dem Betrüger in XVG verschollen!
Grüße
Also sorry, und Danke!
Thank you for taking the scammers C-CEX from your website! Thank you! I hope I was the last of these used!
I would like to donate as well.
But all my liquidity has disappeared on C-CEX at the scam in XVG!
greetings
So sorry, and thanks!
Hallo Verge-Team.
Danke das ihr die Betrüger C-CEX von eurer Website genommen habt! Danke! Ich hoffe ich war der letzte der diesen nutzte!
Ich würde gerne auch spenden.
Aber meine ganze Liquidität ist auf C-CEX bei dem Betrüger in XVG verschollen!
Grüße
Also sorry, und Danke!
Anyone know what happened to the whale that had 200 million XVG on c-cex?
If i had 200 million XVG i would definately not put it on C-CEX! lol, supprised there would be so much on the exchange in total!
The value of thoose is about 16x the daily trade volume of C-Cex total
If my collected records are correct. On c-cex about 20,000,000 XVG have disappeared!
The price was on 19.12.17 (day of the blockade) $ 0.045
So about $ 900,000
(25.12.17 - 0,22$ = 4.400.000$)
But since the sales orders (xvgct) sometimes exceed 190,000,000, it is clear that they can put in as many xvgct as they need for pricing !!!
So c-cex cheat in public !!
greetings
i have written the admin of c-cex asking for a public address that i can see the funds in, since he claims they are not accessible, we should be able to see them there, not move forever
Is there an answer from the c-cex administrator?
greetings
Time will tell. Announcement to be made on either the 16th or 17th April.
Any1 heard of rumors about XVG and Amazon partnership?
Nope.This is the problem, people will guess between now and the 16th April and the price will react to those guesses. The price shot up yesterday on the back of the Amazon Rumour. There was no reason at all for the price rise yesterday which means it will be followed by a dip.
Verge rose on the back of the 'crowdfunding' last week, then dropped after they announced there would be an announcement yet it then shoots up yesterday with no news. That aint right and you know that will be followed by a drop.
in the way you might be correct, but way before any kind of news, just by carefully studying the trading charts, it was clear that the price was about to shoot up, and i believe it will do lot more, please do careful homework, after all it's a trading market. thanks
And not long after writing it the price drops. I am very careful and I study the charts and do my homework. I have been a big supporter of Verge for ages and that's why it is important to ive hints where we can why things go up and down. it shouldn't take 5 days after an announcement about an announcement coming for it to shootup.
The news will be good for Verge but leading up to it we will see swings up and down for whales to fatten their stacks for that announcement.
Can anyone help ? I installed the 'Windows Electrum Wallet' but it will not connect to the network, I've given it access through the firewall but still no network connection, how do I get it connected ?
Use these nodes:
e1.verge-electrum.com port:50003 or port:50002
e2.verge-electrum.com port:50003 or port:50002
e3.verge-electrum.com port:50003 or port:50002
Thanks, that worked. I used the 'e3.verge-electrum.com port:50002' it finally connected after many false starts with all 3 suggested nodes, it still keeps jumping from "Balance: 0.00 XVG" to "Not Connected"/"Synchronizing..." every few seconds, is this normal ?
yes. it connects every x minutes. (as i understand it)
Jump to: