Quote from: bododk on April 07, 2018, 02:36:37 PM

Quote from: siege3967 on April 07, 2018, 01:50:46 PM

Quote from: vitaminas on April 07, 2018, 01:38:00 PM

Quote from: siege3967 on April 07, 2018, 01:31:02 PM

Quote from: vitaminas on April 07, 2018, 01:24:22 PM

Quote from: siege3967 on April 07, 2018, 01:13:01 PM

Lol apparently it was fixed. Yet I found some pretty weirdly mistimed blocks recently. Posting proof of admin saying it's fixed and the blocks. https://ibb.co/ipO5zx
https://ibb.co/fN0URc

it was not fixed yet. It will be fixed with fork at block 2042000

Did you see the screenshots? Admin claims it's fixed

he is not VergeDev he tough it was but its not also if you look at github you can see the code there for several hours already.

+static const int ALGO_RULES_SWITCH_BLOCK = 2042000;
+static const int SAME_ALGO_MAX_COUNT = 5;

http://prntscr.com/j254xz

Okay let's just wait till that block. If it even comes... Blocks are getting repeated in the explorer lol. Also you didn't reply to my responses about the dev saying private ledger goes against his ideologies while still blatantly liying to his sheep followers about their being a private ledger. You're an example of that right here

did you even read my post https://bitcointalk.org/index.php?topic=3256693.msg34151405#msg34151405?

wtf men... why is so hard to understand that a block can have multiple transactions in it and that the information is shown on the #explorer base on transactions not blocks

Umm before the "maintenance", it was represented the normal way. Now it's been changed. Why would it be changed randomly?