Pages:
Author

Topic: Network Attack on XVG / VERGE - page 8. (Read 29534 times)

jr. member
Activity: 69
Merit: 1
May 31, 2018, 03:46:30 AM
Not seeing too much similarity. Anyway, that doesn't matter because you most definitely copied your code from somewhere else. All of us know that your coin is literally a mish-mash of copy-pasted.
you are actually being ridiculous at this point because if you gonna talk about copy then you have to include all the crypto space starting by the second oldest coin LTC that is basically a copy pasta of BTC with some changes and it goes on and on the the rest of the coins so what is your exact point?
jr. member
Activity: 69
Merit: 1
May 31, 2018, 03:43:26 AM
Well, its all over Social Media now that XVG's code is flawed, Sunerok doesnt have the capability to fix the code on his own so he needs to copy Shields code. Then blatantly lie about it in public.

https://www.reddit.com/r/CryptoCurrency/comments/8nf4su/shield_uncovers_verge_xvg_deception/

https://twitter.com/coin_wars/status/1002026270530551808

Do your own research
you mean shield the coin that is a fork of XVG? What moral do they have to talk about copy past?? Irony at his best.
jr. member
Activity: 42
Merit: 1
May 31, 2018, 02:48:34 AM
Not seeing too much similarity. Anyway, that doesn't matter because you most definitely copied your code from somewhere else. All of us know that your coin is literally a mish-mash of copy-pasted.
sr. member
Activity: 1021
Merit: 324
legendary
Activity: 1181
Merit: 1018
May 31, 2018, 02:25:11 AM
this thread is entertaining to watch!
member
Activity: 118
Merit: 10
May 31, 2018, 01:14:30 AM

Shield hasnt done anything wrong, you can copy code but claiming the code as your own is a different story. It shows your lack of skills as a dev and that its quite possible you allowed the attacks to happen in the first place

You might want to read this https://opensource.guide/legal/

legendary
Activity: 1708
Merit: 1009
$XVG - The Standard in Crypto as a Currency!
member
Activity: 118
Merit: 10
May 30, 2018, 11:11:16 PM
Well, its all over Social Media now that XVG's code is flawed, Sunerok doesnt have the capability to fix the code on his own so he needs to copy Shields code. Then blatantly lie about it in public.

https://www.reddit.com/r/CryptoCurrency/comments/8nf4su/shield_uncovers_verge_xvg_deception/

https://twitter.com/coin_wars/status/1002026270530551808

Do your own research
hero member
Activity: 1050
Merit: 604
May 30, 2018, 08:57:51 PM
In their twitter account they said that this claims are FUD's and the XVG is unaffected.. I really dont trust these developers now if XVG is really unaffected then why in the hell its dropping like crazy these past weeks

How can you not trust a coin that has been "hacked" so many times?

You are nothing but an evil fudder.

HODL!!!
sr. member
Activity: 644
Merit: 251
May 30, 2018, 07:22:05 PM
In their twitter account they said that this claims are FUD's and the XVG is unaffected.. I really dont trust these developers now if XVG is really unaffected then why in the hell its dropping like crazy these past weeks
full member
Activity: 406
Merit: 100
Radix-The Decentralized Finance Protocol
May 30, 2018, 06:41:36 PM
With each attack, the price falls smoothly ... It seems to me that either some of the holders know this or their belief in a coin and its bright future is very strong) We are waiting for a double 4 and developers' excuses Grin
jr. member
Activity: 126
Merit: 2
May 30, 2018, 06:20:40 PM
Regardless, we know that these are malicious blocks. No denying that. The attackers were "able to mine" 4 - 5 blocks per second (AT LEAST) at incredibly low difficulty, and insert them into the chain as valid.

THE PROBLEM HERE IS THAT IN BETWEEN these blocks below, there are withdrawal transactions TOTALING MORE THAN the attacker wallet ever had credited to their account. Hence, double spend attack and minting counterfeit Verge.

Code:
2205923 - 62b24a19f15716f1679bad531ef4b7c14b3d58d980c5490a0a135c2b1857a139	2018-05-22 07:55:17	lyra2re
2205922 - f11c4423c21bbe77907937ea40d45ad69572498f2ee3d160b90c0afed2b941cf 2018-05-22 07:55:17 lyra2re
2205921 - 65ecfa324c69ff64fcbb6657eb70e981289f0b6c922435c89db3451ab0f960e4 2018-05-22 07:55:17 lyra2re
2205920 - 03fd6163763bd2d686d39ae6e1c3b4663cdaed206e7ea0284e847d13e6d6198c 2018-05-22 07:55:17 lyra2re
2205919 - 7e458fc3c5706ec9ddf95cedc254d616dda49764d0c34f788d5bd92519cff0ca 2018-05-22 07:55:16 lyra2re
2205918 - 078ddfdc760995dbb96ccce33fc37dec853f1465b95eeb87bd499048f7e6333b 2018-05-22 07:55:16 lyra2re
2205917 - 00000000083bb16892848cc890317370315f52ed3566e364c4264be4e20f77de 2018-05-22 07:55:16 scrypt
2205916 - 000000001a16b654d11d879efc7bb9fef711f946c69df324a1cc5a2fb240a4a6 2018-05-22 07:55:16 scrypt
2205915 - 0000000004b4258574fefe34f3a0690ff3d8d7050fc67773ff5e349767306086 2018-05-22 07:55:16 scrypt
2205914 - 000000000d2edddbc12448148b710c4c49794e6e74fb820069377da1633dd447 2018-05-22 07:55:16 scrypt
2205913 - 000000001f507a7a23a1a55860c19c1226d5edba0453043db4b884cb6de5c028 2018-05-22 07:55:15 scrypt
2205912 - 0000000049fb9df391abbd8ab42cdb77cffb7b4941bb65ed3aa5589a100e8594 2018-05-22 07:55:15 scrypt
2205911 - 81e8d7899d20b0e1ea00a458e92bffc4716389e55cf3e4947d44eed220e873b8 2018-05-22 07:55:15 lyra2re
2205910 - 70d35dbf84cbf4a1b3cd1ed2e12d65c4e0776c2186aa1cec956b7c7382b7b6a3 2018-05-22 07:55:15 lyra2re
2205909 - d8017bd566bcc7359c6b995357756fccb325e1a8ef0e6153c7587c1434dc982b 2018-05-22 07:55:15 lyra2re
2205908 - 2079b84323d04234895f4ee6da8c28518b52e97b59da4501a1195349f9f94467 2018-05-22 07:55:15 lyra2re
2205907 - 0d14bc8be431ae5734c8cd791cf5e285338a5cec1a8bb4c9849209da5921b77b 2018-05-22 07:55:14 lyra2re
2205906 - f6a63a5c746b91d4ab6f79aaa799c80e899d2026032c515a2cf482bd0e97b85f 2018-05-22 07:55:14 lyra2re
2205905 - 000000001a8645b501a5ca405883c34aa0c5edebfe4343ed967d978e66a45d95 2018-05-22 07:55:14 scrypt
2205904 - 00000000233ee973c1ee798b3ae073953bc43b0280e5eef9bfeaea15c8c44c60 2018-05-22 07:55:14 scrypt
2205903 - 000000000326ed66ebda4c4b0c391757648ecf6668d2da9b1ab03d19ecc46bcf 2018-05-22 07:55:14 scrypt
2205902 - 000000007f4bf76e0bc1f0ecabeac939f924dde177d01364a725778902a5565b 2018-05-22 07:55:14 scrypt
2205901 - 0000000050dd9cea6865263e4f64f8121560476ce400803dedf2c34e68b1c971 2018-05-22 07:55:13 scrypt
2205900 - 00000000a8c64d3176a056c35722f9255e5231191d4b5dfc2f039256586d3ad8 2018-05-22 07:55:13 scrypt
2205899 - f3dad3e853a58619319bdfa4c193c66f21b361325d8b22776d05bd2938ea5947 2018-05-22 07:55:13 lyra2re
2205898 - 98fa3326d7691819571afdf8967d1a78ca94d6a0e7e6628c23eef5483bd763b3 2018-05-22 07:55:13 lyra2re
2205897 - e40345cc328610a0f2d81561045af02ad8baff7dd1995a63f79934de4adab930 2018-05-22 07:55:13 lyra2re
2205896 - 9db9b6b3b0db02ca57f1efcacf2d9375b9ae5755ead87e3fb990d74eda4da5de 2018-05-22 07:55:13 lyra2re
2205895 - 301d784a47323c22fc9f5301413f6626c6cb156346d26c81e619288deea98050 2018-05-22 07:55:12 lyra2re
2205894 - 6245c040a61adcc9113328395c8fa000a621685ba762866b24a28c23e05ee06d 2018-05-22 07:55:12 lyra2re
2205893 - 2018-05-22 07:55:12 - 1.09806977
2205892 - 2018-05-22 07:55:12 - 0.64576046
2205891 - 2018-05-22 07:55:12 - 0.6194293
2205890 - 2018-05-22 07:55:12 - 0.58566207
2205889 - 2018-05-22 07:55:11 - 0.42515164
2205888 - 2018-05-22 07:55:11 - 0.41638076
2205887 - 2018-05-22 07:55:11 - 0.49013889
2205886 - 2018-05-22 07:55:11 - 0.37362318
2205885 - 2018-05-22 07:55:11 - 0.36795297
2205884 - 2018-05-22 07:55:11 - 0.35867531
2205883 - 2018-05-22 07:55:10 - 0.29126408
2205882 - 2018-05-22 07:55:10 - 0.28904806
2205881 - 2018-05-22 07:55:10 - 0.28904806
2205880 - 2018-05-22 07:55:10 - 0.31913961
newbie
Activity: 6
Merit: 0
May 30, 2018, 06:03:16 PM
I really just want a simple question answered.

JUSTIN: Would that be possible? Can you answer?

Why does this sampling of blocks from 2205900 -> 2205923  - which were added to the chain as valid, only switch between 2 different algo's? According to the consensus code in Verge, shouldn't these have been discarded as invalid?


Code:
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 - 0000000050dd9cea6865263e4f64f8121560476ce400803dedf2c34e68b1c971 22nd May 2018 06:55:13 scrypt
2205900 - 00000000a8c64d3176a056c35722f9255e5231191d4b5dfc2f039256586d3ad8 22nd May 2018 06:55:13 scrypt



Well, no, this is allowed. This is the commit that mitigate the timewarp attack using a single algorithm https://github.com/vergecurrency/VERGE/commit/80c81aef63272231fc39c2af4b8db9f3f2e9d328
It seems that the purpose of the patch is to only allow 5 of the last teen blocks to be mined with the same algorithm, which it seems to achive (there seems to be a small bug which allows 6 blocks with the same algorithm in a row. Not sure if that is on purpose, but it is probably not too critical).

Ummmmm that's not how coding works. If it's programmed to only let 5, it should not let 6. So either his code is flawed or there's another exploit they're using.

I linked to the code, you could just read it you know...

Anyway:
AcceptBlock() checks if the newly submitted block is valid.  One of the checks is calling CheckPrevAlgo() with the parent block to the one being checked.
CheckPrevAlgo() checks if more than SAME_ALGO_MAX_COUNT (5) of the previous SAME_ALGO_MAX_COUNT*2 (10) blocks are mined using the same algorithm as the one being checked. if so, it is invalid. This means that a block is valid if no more than 5 of the previous 10 blocks where mined using the algorithm for the block being tested, leading to 6 of any 11 subsequent blocks can have the same algorithm.

I think the intent was to only allow 5 blocks with the same algorithm in a group of 10 blocks, so it appears to be a bit buggy, but as i said, i don't think it makes much of a difference as it still prevents the chain to be mined only with one algorithm, which was the intent.

It seems that there are much worse issues with Verge such as measuring chain trust simply based on the length of the chain as well as the ability to game the difficulty adjustment to force the difficulty down. We should probably focus on those issues instead of some comparatively unimportant oversight in how the rule to prevent blocks only being mined with a single algorithm was implemented.
jr. member
Activity: 42
Merit: 1
May 30, 2018, 05:41:17 PM
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.

Lolololol. Offending normal people ( which i dont ) or FUDDers ( which i will always) like you? I give FUDders extra treatment. Get used to my offensive behaviour until you keep spreading fake shit and asking vague question again and again to prove your shitty thing.

Let's get into technicalities. Very isn't even private. There is no private transaction or private ledger. Wraith is stealth addresses with Tor. All values are visible on the blockchain.

Lol they backpedalled on the private ledger after advertising it so heavily because "it went against their values" or something like that.

I'm gonna look for the post just for the lolz and compare it to what they were proposing for Wraith beforehand.


It's still mentioned in their "blackpaper" 😂
jr. member
Activity: 42
Merit: 1
May 30, 2018, 05:40:11 PM
I really just want a simple question answered.

JUSTIN: Would that be possible? Can you answer?

Why does this sampling of blocks from 2205900 -> 2205923  - which were added to the chain as valid, only switch between 2 different algo's? According to the consensus code in Verge, shouldn't these have been discarded as invalid?


Code:
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 - 0000000050dd9cea6865263e4f64f8121560476ce400803dedf2c34e68b1c971 22nd May 2018 06:55:13 scrypt
2205900 - 00000000a8c64d3176a056c35722f9255e5231191d4b5dfc2f039256586d3ad8 22nd May 2018 06:55:13 scrypt



Well, no, this is allowed. This is the commit that mitigate the timewarp attack using a single algorithm https://github.com/vergecurrency/VERGE/commit/80c81aef63272231fc39c2af4b8db9f3f2e9d328
It seems that the purpose of the patch is to only allow 5 of the last teen blocks to be mined with the same algorithm, which it seems to achive (there seems to be a small bug which allows 6 blocks with the same algorithm in a row. Not sure if that is on purpose, but it is probably not too critical).

Ummmmm that's not how coding works. If it's programmed to only let 5, it should not let 6. So either his code is flawed or there's another exploit they're using.
newbie
Activity: 6
Merit: 0
May 30, 2018, 03:39:23 PM
I really just want a simple question answered.

JUSTIN: Would that be possible? Can you answer?

Why does this sampling of blocks from 2205900 -> 2205923  - which were added to the chain as valid, only switch between 2 different algo's? According to the consensus code in Verge, shouldn't these have been discarded as invalid?


Code:
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 - 0000000050dd9cea6865263e4f64f8121560476ce400803dedf2c34e68b1c971 22nd May 2018 06:55:13 scrypt
2205900 - 00000000a8c64d3176a056c35722f9255e5231191d4b5dfc2f039256586d3ad8 22nd May 2018 06:55:13 scrypt



Well, no, this is allowed. This is the commit that mitigate the timewarp attack using a single algorithm https://github.com/vergecurrency/VERGE/commit/80c81aef63272231fc39c2af4b8db9f3f2e9d328
It seems that the purpose of the patch is to only allow 5 of the last teen blocks to be mined with the same algorithm, which it seems to achive (there seems to be a small bug which allows 6 blocks with the same algorithm in a row. Not sure if that is on purpose, but it is probably not too critical).
jr. member
Activity: 126
Merit: 2
May 30, 2018, 03:12:14 PM
I really just want a simple question answered.

JUSTIN: Would that be possible? Can you answer?

Why does this sampling of blocks from 2205900 -> 2205923  - which were added to the chain as valid, only switch between 2 different algo's? According to the consensus code in Verge, shouldn't these have been discarded as invalid?


Code:
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 - 0000000050dd9cea6865263e4f64f8121560476ce400803dedf2c34e68b1c971 22nd May 2018 06:55:13 scrypt
2205900 - 00000000a8c64d3176a056c35722f9255e5231191d4b5dfc2f039256586d3ad8 22nd May 2018 06:55:13 scrypt

newbie
Activity: 6
Merit: 1
May 30, 2018, 02:07:27 PM
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.

Lolololol. Offending normal people ( which i dont ) or FUDDers ( which i will always) like you? I give FUDders extra treatment. Get used to my offensive behaviour until you keep spreading fake shit and asking vague question again and again to prove your shitty thing.

Let's get into technicalities. Very isn't even private. There is no private transaction or private ledger. Wraith is stealth addresses with Tor. All values are visible on the blockchain.

Lol they backpedalled on the private ledger after advertising it so heavily because "it went against their values" or something like that.

I'm gonna look for the post just for the lolz and compare it to what they were proposing for Wraith beforehand.

newbie
Activity: 6
Merit: 1
May 30, 2018, 02:01:17 PM
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.

Lolololol. Offending normal people ( which i dont ) or FUDDers ( which i will always) like you? I give FUDders extra treatment. Get used to my offensive behaviour until you keep spreading fake shit and asking vague question again and again to prove your shitty thing.


What has boxalex said that is fake or FUD? Nothing that I see.

Your friend box or whatever his name is fishing for anything just like rest of fudders. This thread was supposed to be on the alleged attack on Verge Network, which was unsuccessfull. Yet, he keeps going OFFTOPIC, now that sockpuppet of OCMiner chose a topic on Blockexplorer bug. I mean What the F? It seems like he wants to keep this discussion to go on forever.
It seems like we have a collection of Banned people over here.

Ya'all have adopted motto
" IF YOU CANT MAKE IT, FAKE IT "

This thread was started during the first attack back in April and continued to stay alive because of new attacks? Even though the latest attack was unsuccessful, the fact of the matter is that attempts are being made which warrants the existence of a place where these issue can be discussed.

You on the other hand have only responded with insults and 0 actual answers to any questions.

All you've manage to do successfully is project your insecurities.

It amazes me always that people with new accounts show up wit to ask same question again and again without even reading the whole post. Literally your account has been used for this thread.
I can bet, that you are one of the same person who were posting FUD and yet created new account to claim your concern.

If you want ur answer really, then have a look at older posts and DYOR.

And it amazed me that one isn't allowed to make an account to a site they've never registered for to be able discuss an issue of interest. I mean.. What the fuck is the point of forums existing... right? Not unless it's to kiss ass to a coin that is obviously faulty... Right?

I have looked at this thread since it was first created in April, and a lot of the questions that have been asked in the last few days simply have gone ignored. A lot of questions even before the last two legit attacks went unanswered because the issue was "fixed"...

People like you are why the general crypto community hates Verge. This will never change. Period. Stop deflecting you insecure child.

Either you start helping others out by linking them to sources, or shut the fuck and stop screaming FUD, because clearly you're doing nothing to help prevent the FUD...

Say what you want at this point. What's gonna matter more than words in the long run is legit progress from the Verge team, so I'll leave it at that.

Pages:
Jump to: