Dry Run 7: The Power of DPOS

[toast]

We're taking this one down. Great success all around, except for our sloppy hard fork at the end.

Next test net:

* 10 transactions per second
* 10 second blocks
* Bids/asks/shorts (but no order matching, ha ha)

[alexxy]

Vote also for some of my delegates =D

[cass]

DAC Unlimited is trusted.

is it an Hyperetas project!? So i could help on design if needed!?

[cass]

wow,poor network now! What happening?

latest github master has a bug that makes client stuck on a block .. no idea when they will update that :(

guess we'll start a new Dry Run today... or better asap .. no exact timeframe currently

[cass]

It should be very useful having some short time analytics on the delegate behavior to take decision in events like this one.

+5%

Also we need auto-voting to kick out non-producing delegates

+5%

[emski]

It should be very useful having some short time analytics on the delegate behavior to take decision in events like this one.

+5%

Also we need auto-voting to kick out non-producing delegates

Without negative votes that might be a little difficult to accomplish.

[spartako]

It should be very useful having some short time analytics on the delegate behavior to take decision in events like this one.

+5%

Also we need auto-voting to kick out non-producing delegates

+5%

[xeroc]

It should be very useful having some short time analytics on the delegate behavior to take decision in events like this one.

+5%

Also we need auto-voting to kick out non-producing delegates

[spartako]

what's going on?
the security state turn to red alert!

There's a sync bug in the git-master .. and a few delegates have a auto-make toolchain installed .. so they cant sync atm ..

It is a good opportunity to act like we would on the real chain...
we can vote up delegates that successfully produced the last blocks and some stand-by delegates to test them out and take our votes back for delegates that lost the last blocks (even if they have over all great statistics)....
That action will be temporary until "blockchain_average_delegate_participation" is over 70% again for example.... When we know that we have the problem behind us (bug,attacks ddos etc.) we can vote again our favorite delegates....)


PS
It would be great if there was available a command that informed us which delegates  has missed their last 5 blocks for example and which one produced successful their last 5...
so we could very quick make the "right" votes to bring the network to a better "blockchain_average_delegate_participation" percentage...

I voted for you and now you are in the top 100:

Code Select Expand


334   liondani                        0.0505564810 % 64       1        98.46 %       99 %     0.45385 XTS     14534     

Do you have other delegates so I can vote for them?

It should be very useful having some short time analytics on the delegate behavior to take decision in events like this one.

[liondani]

what's going on?
the security state turn to red alert!

There's a sync bug in the git-master .. and a few delegates have a auto-make toolchain installed .. so they cant sync atm ..

It is a good opportunity to act like we would on the real chain...
we can vote up delegates that successfully produced the last blocks and some stand-by delegates to test them out and take our votes back for delegates that lost the last blocks (even if they have over all great statistics)....
That action will be temporary until "blockchain_average_delegate_participation" is over 70% again for example.... When we know that we have the problem behind us (bug,attacks ddos etc.) we can vote again our favorite delegates....)


PS
It would be great if there was available a command that informed us which delegates  has missed their last 5 blocks for example and which one produced successful their last 5...
so we could very quick make the "right" votes to bring the network to a better "blockchain_average_delegate_participation" percentage...

[CalabiYau]

what's going on?
the security state turn to red alert!

There's a sync bug in the git-master .. and a few delegates have a auto-make toolchain installed .. so they cant sync atm ..

Thx for the info, everything is stuck (new win7 gui & new git version)

[lzr1900]

what's going on?
the security state turn to red alert!

There's a sync bug in the git-master .. and a few delegates have a auto-make toolchain installed .. so they cant sync atm ..

～So that is what it is. thanks.

[xeroc]

what's going on?
the security state turn to red alert!

There's a sync bug in the git-master .. and a few delegates have a auto-make toolchain installed .. so they cant sync atm ..

[lzr1900]

what's going on?
the security state turn to red alert!

[yangsbo]

why my mac client always told me" wrong password "!I input it absolutely correct.

me too
input password ,then wrong password
you can use" go to account" into main windows