Topic: Network Attack on XVG / VERGE - page 10. (Read 29534 times)
lets dump this malicious coin to 1 sat or lower .. may be dev exploiting the coin to make huge money
iquidus has alot of bugs. prohashing and other yiimp based explorers are far more accurate.
Just out of curiousity in case your statement here is indeed the case (and i have some doubts about it), but just in case.
- So why is Verge using the most bugged explorer for its own currency?
- What's the prupose of having an official explorer nobody can rely on?
- What explorer do you use than while doing your own research/investigation if the official Verge Explorer can't be trusted due it's bugs?
- Was the possibility that the explorer shows the correct value actually investigated or you just think it's a bug?
- Any reference or example where this bug elsewhere happened and shows negative balance?
And there is still no answer to a whole lot of valid questions, maybe you won't to take a look into them as well.
P.S.: IF this guy here posting and offending people en mass here with lowest street language is really your moderator on the telegram channel
and representing Verges views/spirit/interest, than you should think about what bad taste such behavour leaves associated with Verge.
Just as a thought and side note.
I have some more legitimate questions about features Verge presents itself as having: https://vergecurrency.com/key-tech/
1. Atomic Swaps - atomic cross-chain trading
- If this functionality is actually present, can you please point me to instructions on how to perform an atomic swap, off chain?
- With what other coins are swaps supported?
2. P2P integrations
- Your website says Verge is integrated into messaging on Discord, Slack, Twitter and Telegram. How would I, as a user of each of these platforms, use this function?
No comment? Anyone from Verge care to? VergeDev?
With regards to the negative balance.. To me, it looks like so-called "double spend", or basically printing counterfeit xvg. However, we can't really rely so much on this (OFFICIAL) block explorer since it it buggy and confirmed unreliable by Verge Dev himself a few pages back. And why bother downloading my own copy of the blockchain anyways? Not going to waste my time knowing that the chain is completely compromised and can no longer be trusted. So, we just have to dig a bit deeper and go with the information available to us.
Anyhow, if we take a sampling of transactions in address - D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp - and look up the corresponding block info, we see some odd stuff.
Beginning with block height 2205923 and moving backwards ~> 2205900 - with the initial sampling composed of all debits (spend), and then filling in the missing blocks from 2205900 - 2205923 (I don't care about transactions which are deposits/credits [only debits/spend]).
23 blocks all with lyra2re and scrypt algo mined in what, 5 seconds? Hmm. I thought the first fix was supposed to prevent the same algo from being used that many times in consecutive blocks.
All blocks confirmed as VALID using data from poolovich - http://poolovich.pro/explorer/XVG
( Thanks for the TIP on that explorer Justin, it works well! [And by the way, is it really so hard to get a working Iquidus Explorer up? Hundreds of coins I've looked at and xvg seems to be the only one with an issue i've found. Just wondering] ) . . .
Maybe I'm missing something (hey, it happens), but this does not look OK to me.
With regards to the negative balance.. To me, it looks like so-called "double spend", or basically printing counterfeit xvg. However, we can't really rely so much on this (OFFICIAL) block explorer since it it buggy and confirmed unreliable by Verge Dev himself a few pages back. And why bother downloading my own copy of the blockchain anyways? Not going to waste my time knowing that the chain is completely compromised and can no longer be trusted. So, we just have to dig a bit deeper and go with the information available to us.
Anyhow, if we take a sampling of transactions in address - D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp - and look up the corresponding block info, we see some odd stuff.
Beginning with block height 2205923 and moving backwards ~> 2205900 - with the initial sampling composed of all debits (spend), and then filling in the missing blocks from 2205900 - 2205923 (I don't care about transactions which are deposits/credits [only debits/spend]).
23 blocks all with lyra2re and scrypt algo mined in what, 5 seconds? Hmm. I thought the first fix was supposed to prevent the same algo from being used that many times in consecutive blocks.
All blocks confirmed as VALID using data from poolovich - http://poolovich.pro/explorer/XVG
( Thanks for the TIP on that explorer Justin, it works well! [And by the way, is it really so hard to get a working Iquidus Explorer up? Hundreds of coins I've looked at and xvg seems to be the only one with an issue i've found. Just wondering] ) . . .
Code:
Height - Block hash Time stamp Algo used
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2205923 - 62b24a19f15716f1679bad531ef4b7c14b3d58d980c5490a0a135c2b1857a139 22nd May 2018 06:55:17 lyra2re
2205922 - f11c4423c21bbe77907937ea40d45ad69572498f2ee3d160b90c0afed2b941cf 22nd May 2018 06:55:17 lyra2re
2205921 - 65ecfa324c69ff64fcbb6657eb70e981289f0b6c922435c89db3451ab0f960e4 22nd May 2018 06:55:17 lyra2re
2205920 - 03fd6163763bd2d686d39ae6e1c3b4663cdaed206e7ea0284e847d13e6d6198c 22nd May 2018 06:55:17 lyra2re
2205919 - 7e458fc3c5706ec9ddf95cedc254d616dda49764d0c34f788d5bd92519cff0ca 22nd May 2018 06:55:16 lyra2re
2205918 - 078ddfdc760995dbb96ccce33fc37dec853f1465b95eeb87bd499048f7e6333b 22nd May 2018 06:55:16 lyra2re
2205917 - 00000000083bb16892848cc890317370315f52ed3566e364c4264be4e20f77de 22nd May 2018 06:55:16 scrypt
2205916 - 000000001a16b654d11d879efc7bb9fef711f946c69df324a1cc5a2fb240a4a6 22nd May 2018 06:55:16 scrypt
2205915 - 0000000004b4258574fefe34f3a0690ff3d8d7050fc67773ff5e349767306086 22nd May 2018 06:55:16 scrypt
2205914 - 000000000d2edddbc12448148b710c4c49794e6e74fb820069377da1633dd447 22nd May 2018 06:55:16 scrypt
2205913 - 000000001f507a7a23a1a55860c19c1226d5edba0453043db4b884cb6de5c028 22nd May 2018 06:55:15 scrypt
2205912 - 0000000049fb9df391abbd8ab42cdb77cffb7b4941bb65ed3aa5589a100e8594 22nd May 2018 06:55:15 scrypt
2205911 - 81e8d7899d20b0e1ea00a458e92bffc4716389e55cf3e4947d44eed220e873b8 22nd May 2018 06:55:15 lyra2re
2205910 - 70d35dbf84cbf4a1b3cd1ed2e12d65c4e0776c2186aa1cec956b7c7382b7b6a3 22nd May 2018 06:55:15 lyra2re
2205909 - d8017bd566bcc7359c6b995357756fccb325e1a8ef0e6153c7587c1434dc982b 22nd May 2018 06:55:15 lyra2re
2205908 - 2079b84323d04234895f4ee6da8c28518b52e97b59da4501a1195349f9f94467 22nd May 2018 06:55:15 lyra2re
2205907 - 0d14bc8be431ae5734c8cd791cf5e285338a5cec1a8bb4c9849209da5921b77b 22nd May 2018 06:55:14 lyra2re
2205906 - f6a63a5c746b91d4ab6f79aaa799c80e899d2026032c515a2cf482bd0e97b85f 22nd May 2018 06:55:14 lyra2re
2205905 - 000000001a8645b501a5ca405883c34aa0c5edebfe4343ed967d978e66a45d95 22nd May 2018 06:55:14 scrypt
2205904 - 00000000233ee973c1ee798b3ae073953bc43b0280e5eef9bfeaea15c8c44c60 22nd May 2018 06:55:14 scrypt
2205903 - 000000000326ed66ebda4c4b0c391757648ecf6668d2da9b1ab03d19ecc46bcf 22nd May 2018 06:55:14 scrypt
2205902 - 000000007f4bf76e0bc1f0ecabeac939f924dde177d01364a725778902a5565b 22nd May 2018 06:55:14 scrypt
2205901 - 0000000050dd9cea6865263e4f64f8121560476ce400803dedf2c34e68b1c97122nd May 2018 06:55:13 scrypt
2205900 - 00000000a8c64d3176a056c35722f9255e5231191d4b5dfc2f039256586d3ad8 22nd May 2018 06:55:13 scrypt
**Note** timestamp data manually set back 1 hour to match that of Verge Explorer. For whatever reason, poolovich 1 hour ahead.++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2205923 - 62b24a19f15716f1679bad531ef4b7c14b3d58d980c5490a0a135c2b1857a139 22nd May 2018 06:55:17 lyra2re
2205922 - f11c4423c21bbe77907937ea40d45ad69572498f2ee3d160b90c0afed2b941cf 22nd May 2018 06:55:17 lyra2re
2205921 - 65ecfa324c69ff64fcbb6657eb70e981289f0b6c922435c89db3451ab0f960e4 22nd May 2018 06:55:17 lyra2re
2205920 - 03fd6163763bd2d686d39ae6e1c3b4663cdaed206e7ea0284e847d13e6d6198c 22nd May 2018 06:55:17 lyra2re
2205919 - 7e458fc3c5706ec9ddf95cedc254d616dda49764d0c34f788d5bd92519cff0ca 22nd May 2018 06:55:16 lyra2re
2205918 - 078ddfdc760995dbb96ccce33fc37dec853f1465b95eeb87bd499048f7e6333b 22nd May 2018 06:55:16 lyra2re
2205917 - 00000000083bb16892848cc890317370315f52ed3566e364c4264be4e20f77de 22nd May 2018 06:55:16 scrypt
2205916 - 000000001a16b654d11d879efc7bb9fef711f946c69df324a1cc5a2fb240a4a6 22nd May 2018 06:55:16 scrypt
2205915 - 0000000004b4258574fefe34f3a0690ff3d8d7050fc67773ff5e349767306086 22nd May 2018 06:55:16 scrypt
2205914 - 000000000d2edddbc12448148b710c4c49794e6e74fb820069377da1633dd447 22nd May 2018 06:55:16 scrypt
2205913 - 000000001f507a7a23a1a55860c19c1226d5edba0453043db4b884cb6de5c028 22nd May 2018 06:55:15 scrypt
2205912 - 0000000049fb9df391abbd8ab42cdb77cffb7b4941bb65ed3aa5589a100e8594 22nd May 2018 06:55:15 scrypt
2205911 - 81e8d7899d20b0e1ea00a458e92bffc4716389e55cf3e4947d44eed220e873b8 22nd May 2018 06:55:15 lyra2re
2205910 - 70d35dbf84cbf4a1b3cd1ed2e12d65c4e0776c2186aa1cec956b7c7382b7b6a3 22nd May 2018 06:55:15 lyra2re
2205909 - d8017bd566bcc7359c6b995357756fccb325e1a8ef0e6153c7587c1434dc982b 22nd May 2018 06:55:15 lyra2re
2205908 - 2079b84323d04234895f4ee6da8c28518b52e97b59da4501a1195349f9f94467 22nd May 2018 06:55:15 lyra2re
2205907 - 0d14bc8be431ae5734c8cd791cf5e285338a5cec1a8bb4c9849209da5921b77b 22nd May 2018 06:55:14 lyra2re
2205906 - f6a63a5c746b91d4ab6f79aaa799c80e899d2026032c515a2cf482bd0e97b85f 22nd May 2018 06:55:14 lyra2re
2205905 - 000000001a8645b501a5ca405883c34aa0c5edebfe4343ed967d978e66a45d95 22nd May 2018 06:55:14 scrypt
2205904 - 00000000233ee973c1ee798b3ae073953bc43b0280e5eef9bfeaea15c8c44c60 22nd May 2018 06:55:14 scrypt
2205903 - 000000000326ed66ebda4c4b0c391757648ecf6668d2da9b1ab03d19ecc46bcf 22nd May 2018 06:55:14 scrypt
2205902 - 000000007f4bf76e0bc1f0ecabeac939f924dde177d01364a725778902a5565b 22nd May 2018 06:55:14 scrypt
2205901 - 0000000050dd9cea6865263e4f64f8121560476ce400803dedf2c34e68b1c97122nd May 2018 06:55:13 scrypt
2205900 - 00000000a8c64d3176a056c35722f9255e5231191d4b5dfc2f039256586d3ad8 22nd May 2018 06:55:13 scrypt
Maybe I'm missing something (hey, it happens), but this does not look OK to me.
P.S.: IF this guy here posting and offending people en mass here with lowest street language is really your moderator on the telegram channel
and representing Verges views/spirit/interest, than you should think about what bad taste such behavour leaves associated with Verge.
Just as a thought and side note.
and representing Verges views/spirit/interest, than you should think about what bad taste such behavour leaves associated with Verge.
Just as a thought and side note.
Like I mentioned yesterday, their mod was making jokes (what I would like to assume are jokes) about murdering folks over here. Not really funny if you ask me.
......
seriously, it's not really the right place in this thread to promote another coin.....
It is when the coin that is getting shafted NEVER listened to the DEVS of DAPS in regards to a fix for these time warp attacks
Considering that chart is a complete lie it's hard to believe anything else you say.
iquidus has alot of bugs. prohashing and other yiimp based explorers are far more accurate.
Just out of curiousity in case your statement here is indeed the case (and i have some doubts about it), but just in case.
- So why is Verge using the most bugged explorer for its own currency?
- What's the prupose of having an official explorer nobody can rely on?
- What explorer do you use than while doing your own research/investigation if the official Verge Explorer can't be trusted due it's bugs?
- Was the possibility that the explorer shows the correct value actually investigated or you just think it's a bug?
- Any reference or example where this bug elsewhere happened and shows negative balance?
And there is still no answer to a whole lot of valid questions, maybe you won't to take a look into them as well.
P.S.: IF this guy here posting and offending people en mass here with lowest street language is really your moderator on the telegram channel
and representing Verges views/spirit/interest, than you should think about what bad taste such behavour leaves associated with Verge.
Just as a thought and side note.
No answer from them, but please see what I have posted on the issue.
So far: crickets
iquidus has alot of bugs. prohashing and other yiimp based explorers are far more accurate.
Just out of curiousity in case your statement here is indeed the case (and i have some doubts about it), but just in case.
- So why is Verge using the most bugged explorer for its own currency?
- What's the prupose of having an official explorer nobody can rely on?
- What explorer do you use than while doing your own research/investigation if the official Verge Explorer can't be trusted due it's bugs?
- Was the possibility that the explorer shows the correct value actually investigated or you just think it's a bug?
- Any reference or example where this bug elsewhere happened and shows negative balance?
And there is still no answer to a whole lot of valid questions, maybe you won't to take a look into them as well.
P.S.: IF this guy here posting and offending people en mass here with lowest street language is really your moderator on the telegram channel
and representing Verges views/spirit/interest, than you should think about what bad taste such behavour leaves associated with Verge.
Just as a thought and side note.
How does this explorer bug work when it's supposed to just directly read off the blockchain? So the blockchain is bugged, not the explorer. The other explorer probably deals with negative values as 0.
Correct.
Iquidus Explorer appears to be correctly reporting the balance which has been spent. Meaning, more is being spent than available to. Double spend. The chain is fucked.
Would any verge supporter like to explain this? Negative balance: https://verge-blockchain.info/address/D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp
this thread gets too much watered with intention by the XVG fanboyz. Putting all important unanswered questions at the end of the topic until it's answered .....
what are you? 10yr old?Did you even know how to read. It seems so much hard for yaall to comprehend simple info.
NEGATIVE BALANCE IS AN EXPLORER BUG !!
go to prohashing explorer instead of official vergeexplorer.
How does this explorer bug work when it's supposed to just directly read off the blockchain? So the blockchain is bugged, not the explorer. The other explorer probably deals with negative values as 0.
has any got answer does prohash treat negative balance as zero?
iquidus has alot of bugs. prohashing and other yiimp based explorers are far more accurate.
not an iquidus issue. In fact, it seems to be reporting correctly that double-spends are happening.
Verge coin being 51% attacked the third time was doing the rounds on Reddit that got ruled out as being a FUD. Today, Verge rose in tandem with the crypto market as it registered flecks of green while being officially accepted as the only crypto as a payment by an e-commerce site. Moreover, Verge is hosting its first ever meetup in Amsterdam on June 9.
https://coingape.com/verge-coin-hack-fud-green-myfitstuff-announcement/
https://coingape.com/verge-coin-hack-fud-green-myfitstuff-announcement/
Would any verge supporter like to explain this? Negative balance: https://verge-blockchain.info/address/D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp
this thread gets too much watered with intention by the XVG fanboyz. Putting all important unanswered questions at the end of the topic until it's answered .....
what are you? 10yr old?Did you even know how to read. It seems so much hard for yaall to comprehend simple info.
NEGATIVE BALANCE IS AN EXPLORER BUG !!
go to prohashing explorer instead of official vergeexplorer.
How does this explorer bug work when it's supposed to just directly read off the blockchain? So the blockchain is bugged, not the explorer. The other explorer probably deals with negative values as 0.
has any got answer does prohash treat negative balance as zero?
iquidus has alot of bugs. prohashing and other yiimp based explorers are far more accurate.
Would any verge supporter like to explain this? Negative balance: https://verge-blockchain.info/address/D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp
this thread gets too much watered with intention by the XVG fanboyz. Putting all important unanswered questions at the end of the topic until it's answered .....
what are you? 10yr old?Did you even know how to read. It seems so much hard for yaall to comprehend simple info.
NEGATIVE BALANCE IS AN EXPLORER BUG !!
go to prohashing explorer instead of official vergeexplorer.
How does this explorer bug work when it's supposed to just directly read off the blockchain? So the blockchain is bugged, not the explorer. The other explorer probably deals with negative values as 0.
has any got answer does prohash treat negative balance as zero?
We don't know that it does. And See above
Would any verge supporter like to explain this? Negative balance: https://verge-blockchain.info/address/D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp
this thread gets too much watered with intention by the XVG fanboyz. Putting all important unanswered questions at the end of the topic until it's answered .....
what are you? 10yr old?Did you even know how to read. It seems so much hard for yaall to comprehend simple info.
NEGATIVE BALANCE IS AN EXPLORER BUG !!
go to prohashing explorer instead of official vergeexplorer.
How does this explorer bug work when it's supposed to just directly read off the blockchain? So the blockchain is bugged, not the explorer. The other explorer probably deals with negative values as 0.
has any got answer does prohash treat negative balance as zero?
Again...
With regards to the negative balance.. To me, it looks like so-called "double spend", or basically printing counterfeit xvg. However, we can't really rely so much on this (OFFICIAL) block explorer since it it buggy and confirmed unreliable by Verge Dev himself a few pages back. And why bother downloading my own copy of the blockchain anyways? Not going to waste my time knowing that the chain is completely compromised and can no longer be trusted. So, we just have to dig a bit deeper and go with the information available to us.
Anyhow, if we take a sampling of transactions in address - D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp - and look up the corresponding block info, we see some odd stuff.
Beginning with block height 2205923 and moving backwards ~> 2205900 - with the initial sampling composed of all debits (spend), and then filling in the missing blocks from 2205900 - 2205923 (I don't care about transactions which are deposits/credits [only debits/spend]).
23 blocks all with lyra2re and scrypt algo mined in what, 5 seconds? Hmm. I thought the first fix was supposed to prevent the same algo from being used that many times in consecutive blocks.
All blocks confirmed as VALID using data from poolovich - http://poolovich.pro/explorer/XVG
( Thanks for the TIP on that explorer Justin, it works well! [And by the way, is it really so hard to get a working Iquidus Explorer up? Hundreds of coins I've looked at and xvg seems to be the only one with an issue i've found. Just wondering] ) . . .
Maybe I'm missing something (hey, it happens), but this does not look OK to me.
p.s. Sorry for the crappy formatting.
-C
With regards to the negative balance.. To me, it looks like so-called "double spend", or basically printing counterfeit xvg. However, we can't really rely so much on this (OFFICIAL) block explorer since it it buggy and confirmed unreliable by Verge Dev himself a few pages back. And why bother downloading my own copy of the blockchain anyways? Not going to waste my time knowing that the chain is completely compromised and can no longer be trusted. So, we just have to dig a bit deeper and go with the information available to us.
Anyhow, if we take a sampling of transactions in address - D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp - and look up the corresponding block info, we see some odd stuff.
Beginning with block height 2205923 and moving backwards ~> 2205900 - with the initial sampling composed of all debits (spend), and then filling in the missing blocks from 2205900 - 2205923 (I don't care about transactions which are deposits/credits [only debits/spend]).
23 blocks all with lyra2re and scrypt algo mined in what, 5 seconds? Hmm. I thought the first fix was supposed to prevent the same algo from being used that many times in consecutive blocks.
All blocks confirmed as VALID using data from poolovich - http://poolovich.pro/explorer/XVG
( Thanks for the TIP on that explorer Justin, it works well! [And by the way, is it really so hard to get a working Iquidus Explorer up? Hundreds of coins I've looked at and xvg seems to be the only one with an issue i've found. Just wondering] ) . . .
Code:
Height - Block hash Time stamp Algo used
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2205923 - 62b24a19f15716f1679bad531ef4b7c14b3d58d980c5490a0a135c2b1857a139 22nd May 2018 06:55:17 lyra2re
2205922 - f11c4423c21bbe77907937ea40d45ad69572498f2ee3d160b90c0afed2b941cf 22nd May 2018 06:55:17 lyra2re
2205921 - 65ecfa324c69ff64fcbb6657eb70e981289f0b6c922435c89db3451ab0f960e4 22nd May 2018 06:55:17 lyra2re
2205920 - 03fd6163763bd2d686d39ae6e1c3b4663cdaed206e7ea0284e847d13e6d6198c 22nd May 2018 06:55:17 lyra2re
2205919 - 7e458fc3c5706ec9ddf95cedc254d616dda49764d0c34f788d5bd92519cff0ca 22nd May 2018 06:55:16 lyra2re
2205918 - 078ddfdc760995dbb96ccce33fc37dec853f1465b95eeb87bd499048f7e6333b 22nd May 2018 06:55:16 lyra2re
2205917 - 00000000083bb16892848cc890317370315f52ed3566e364c4264be4e20f77de 22nd May 2018 06:55:16 scrypt
2205916 - 000000001a16b654d11d879efc7bb9fef711f946c69df324a1cc5a2fb240a4a6 22nd May 2018 06:55:16 scrypt
2205915 - 0000000004b4258574fefe34f3a0690ff3d8d7050fc67773ff5e349767306086 22nd May 2018 06:55:16 scrypt
2205914 - 000000000d2edddbc12448148b710c4c49794e6e74fb820069377da1633dd447 22nd May 2018 06:55:16 scrypt
2205913 - 000000001f507a7a23a1a55860c19c1226d5edba0453043db4b884cb6de5c028 22nd May 2018 06:55:15 scrypt
2205912 - 0000000049fb9df391abbd8ab42cdb77cffb7b4941bb65ed3aa5589a100e8594 22nd May 2018 06:55:15 scrypt
2205911 - 81e8d7899d20b0e1ea00a458e92bffc4716389e55cf3e4947d44eed220e873b8 22nd May 2018 06:55:15 lyra2re
2205910 - 70d35dbf84cbf4a1b3cd1ed2e12d65c4e0776c2186aa1cec956b7c7382b7b6a3 22nd May 2018 06:55:15 lyra2re
2205909 - d8017bd566bcc7359c6b995357756fccb325e1a8ef0e6153c7587c1434dc982b 22nd May 2018 06:55:15 lyra2re
2205908 - 2079b84323d04234895f4ee6da8c28518b52e97b59da4501a1195349f9f94467 22nd May 2018 06:55:15 lyra2re
2205907 - 0d14bc8be431ae5734c8cd791cf5e285338a5cec1a8bb4c9849209da5921b77b 22nd May 2018 06:55:14 lyra2re
2205906 - f6a63a5c746b91d4ab6f79aaa799c80e899d2026032c515a2cf482bd0e97b85f 22nd May 2018 06:55:14 lyra2re
2205905 - 000000001a8645b501a5ca405883c34aa0c5edebfe4343ed967d978e66a45d95 22nd May 2018 06:55:14 scrypt
2205904 - 00000000233ee973c1ee798b3ae073953bc43b0280e5eef9bfeaea15c8c44c60 22nd May 2018 06:55:14 scrypt
2205903 - 000000000326ed66ebda4c4b0c391757648ecf6668d2da9b1ab03d19ecc46bcf 22nd May 2018 06:55:14 scrypt
2205902 - 000000007f4bf76e0bc1f0ecabeac939f924dde177d01364a725778902a5565b 22nd May 2018 06:55:14 scrypt
2205901 - 0000000050dd9cea6865263e4f64f8121560476ce400803dedf2c34e68b1c97122nd May 2018 06:55:13 scrypt
2205900 - 00000000a8c64d3176a056c35722f9255e5231191d4b5dfc2f039256586d3ad8 22nd May 2018 06:55:13 scrypt
**Note** timestamp data manually set back 1 hour to match that of Verge Explorer. For whatever reason, poolovich 1 hour ahead.++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2205923 - 62b24a19f15716f1679bad531ef4b7c14b3d58d980c5490a0a135c2b1857a139 22nd May 2018 06:55:17 lyra2re
2205922 - f11c4423c21bbe77907937ea40d45ad69572498f2ee3d160b90c0afed2b941cf 22nd May 2018 06:55:17 lyra2re
2205921 - 65ecfa324c69ff64fcbb6657eb70e981289f0b6c922435c89db3451ab0f960e4 22nd May 2018 06:55:17 lyra2re
2205920 - 03fd6163763bd2d686d39ae6e1c3b4663cdaed206e7ea0284e847d13e6d6198c 22nd May 2018 06:55:17 lyra2re
2205919 - 7e458fc3c5706ec9ddf95cedc254d616dda49764d0c34f788d5bd92519cff0ca 22nd May 2018 06:55:16 lyra2re
2205918 - 078ddfdc760995dbb96ccce33fc37dec853f1465b95eeb87bd499048f7e6333b 22nd May 2018 06:55:16 lyra2re
2205917 - 00000000083bb16892848cc890317370315f52ed3566e364c4264be4e20f77de 22nd May 2018 06:55:16 scrypt
2205916 - 000000001a16b654d11d879efc7bb9fef711f946c69df324a1cc5a2fb240a4a6 22nd May 2018 06:55:16 scrypt
2205915 - 0000000004b4258574fefe34f3a0690ff3d8d7050fc67773ff5e349767306086 22nd May 2018 06:55:16 scrypt
2205914 - 000000000d2edddbc12448148b710c4c49794e6e74fb820069377da1633dd447 22nd May 2018 06:55:16 scrypt
2205913 - 000000001f507a7a23a1a55860c19c1226d5edba0453043db4b884cb6de5c028 22nd May 2018 06:55:15 scrypt
2205912 - 0000000049fb9df391abbd8ab42cdb77cffb7b4941bb65ed3aa5589a100e8594 22nd May 2018 06:55:15 scrypt
2205911 - 81e8d7899d20b0e1ea00a458e92bffc4716389e55cf3e4947d44eed220e873b8 22nd May 2018 06:55:15 lyra2re
2205910 - 70d35dbf84cbf4a1b3cd1ed2e12d65c4e0776c2186aa1cec956b7c7382b7b6a3 22nd May 2018 06:55:15 lyra2re
2205909 - d8017bd566bcc7359c6b995357756fccb325e1a8ef0e6153c7587c1434dc982b 22nd May 2018 06:55:15 lyra2re
2205908 - 2079b84323d04234895f4ee6da8c28518b52e97b59da4501a1195349f9f94467 22nd May 2018 06:55:15 lyra2re
2205907 - 0d14bc8be431ae5734c8cd791cf5e285338a5cec1a8bb4c9849209da5921b77b 22nd May 2018 06:55:14 lyra2re
2205906 - f6a63a5c746b91d4ab6f79aaa799c80e899d2026032c515a2cf482bd0e97b85f 22nd May 2018 06:55:14 lyra2re
2205905 - 000000001a8645b501a5ca405883c34aa0c5edebfe4343ed967d978e66a45d95 22nd May 2018 06:55:14 scrypt
2205904 - 00000000233ee973c1ee798b3ae073953bc43b0280e5eef9bfeaea15c8c44c60 22nd May 2018 06:55:14 scrypt
2205903 - 000000000326ed66ebda4c4b0c391757648ecf6668d2da9b1ab03d19ecc46bcf 22nd May 2018 06:55:14 scrypt
2205902 - 000000007f4bf76e0bc1f0ecabeac939f924dde177d01364a725778902a5565b 22nd May 2018 06:55:14 scrypt
2205901 - 0000000050dd9cea6865263e4f64f8121560476ce400803dedf2c34e68b1c97122nd May 2018 06:55:13 scrypt
2205900 - 00000000a8c64d3176a056c35722f9255e5231191d4b5dfc2f039256586d3ad8 22nd May 2018 06:55:13 scrypt
Maybe I'm missing something (hey, it happens), but this does not look OK to me.
p.s. Sorry for the crappy formatting.
-C
Would any verge supporter like to explain this? Negative balance: https://verge-blockchain.info/address/D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp
this thread gets too much watered with intention by the XVG fanboyz. Putting all important unanswered questions at the end of the topic until it's answered .....
what are you? 10yr old?Did you even know how to read. It seems so much hard for yaall to comprehend simple info.
NEGATIVE BALANCE IS AN EXPLORER BUG !!
go to prohashing explorer instead of official vergeexplorer.
How does this explorer bug work when it's supposed to just directly read off the blockchain? So the blockchain is bugged, not the explorer. The other explorer probably deals with negative values as 0.
OK. This 'XSH copy' shit worries me as a big XVG holder/fan.
I really think the VergeDev needs to answer directly to the accusations and questions mentioned here.
Some show links to codes where XVG is copying another source. Other say the drift fix came 1 month after another coin had the same code!
so what is true or false?
I would like a true explanation from the VerdeDev without the usual 'LOLL'ing'. This is serious business.
The biggest partnership and more to come but you need to be professional about your product and be straight!
So is it all FUD or does it have some truth?
I want proof please.
I really think the VergeDev needs to answer directly to the accusations and questions mentioned here.
Some show links to codes where XVG is copying another source. Other say the drift fix came 1 month after another coin had the same code!
so what is true or false?
I would like a true explanation from the VerdeDev without the usual 'LOLL'ing'. This is serious business.
The biggest partnership and more to come but you need to be professional about your product and be straight!
So is it all FUD or does it have some truth?
I want proof please.
Verge dev has provided proof numerous times all this timestamps posts being shared only shows the half truth. After the first attack verge dev committed and reverted a code on github that some Shield Noobs are claiming to copy. So it practically was committed and reverted and then the second exploit happened, so he had to push the code that was reverted back after first attack that he should not have revert it at first place. In the mean time shield copied the Verge code and pushed the same commit ( that verge dev reverted after first attack)to their repo between 1st and 2nd attack on verge . Hence they are claiming that verge dev copied the code. Its just a publicity stunt. So they are whining abt the credit thing.
Sorry, but i fail to see how this is simply an explorer bug.
Not saying either one of you are right or wrong, but I've had issues with Iquidus where I'd have to wipe the entire DB and start over due to data being corrupt. I guess it could be worthwhile to launch your own XVG explorer.
[/quote]
First Shield Forked from Verge and then they claim of Verge dev copying the code? Cool story dude. 😀
Theres only one way to find out abt new codebase copying. Lets wait for both codebase to release.
[/quote]
I would love to get this validated by VergeDev, those these accusations are from the table.
Would any verge supporter like to explain this? Negative balance: https://verge-blockchain.info/address/D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp
this thread gets too much watered with intention by the XVG fanboyz. Putting all important unanswered questions at the end of the topic until it's answered .....
what are you? 10yr old?Did you even know how to read. It seems so much hard for yaall to comprehend simple info.
NEGATIVE BALANCE IS AN EXPLORER BUG !!
go to prohashing explorer instead of official vergeexplorer.
Sorry, but i fail to see how this is simply an explorer bug.
The issue seems to be that the explorer includes transactions when they have been included in a block, even though those blocks may be orphaned later. However, normally the transactions would simply be included in a block in the new chain instead unless they have been invalidated by another transaction. So it seems that the negative balances could be a result of double spend attempts. If the attempts where successfull is however harder to know.
@boxalex: Thank you for bumping my question, i would still like to see it answered more convincingly by Justin.
@everyone: Please refrain from namecalling and other useless comments in this thread. I would like to discuss the technical issues in XVG. I don't think it is that important who copied code from who, but would rather that the discussion concerns the original topic namely the issues with the verge network and why the attacks on its difficulty adjustment and related problems are possible. If somebody wants to discuss authorship of the code, they could do that in a seperate thread.
Would any verge supporter like to explain this? Negative balance: https://verge-blockchain.info/address/D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp
Its an explorer bug .most probably the iquidus one.
Try using other explorer.
Its normal
Also if you want answer from verge dev then check his previous post.
No, it's not an explorer bug.
Why should anyone accept the answer from the known liar, fraud and/or totally incompetent (not sure yet which) Verge Dev?
It appears to be a bug: https://prohashing.com/explorer/Verge/D7sbycsrSQpj6AjfjsHPb54fvEzN6JH3fp/
I'd still like to hear an explanation about the most recent attack. Giving a 'moving along, nothing to see here' isn't good enough.
https://i.imgur.com/93vFf0o.jpg
https://i.imgur.com/jtG1jy6.jpg
There was a significant drop (90-98% difference) in difficulty for both Scrypt and Lyra2RE. Justin, can you give a detailed explanation of what happened there?
this thread gets too much watered with intention by the XVG fanboyz. Putting all important unanswered questions at the end of the topic until it's answered .....
Lol there was no succesfull attack. Simple. Noobs are gonna be noobs. Seems like OCminer's alleged attack failed
Jump to: