Delegates: Post here once you have upgraded to 0.4.8

[mtang]

mtang.outofcontrol upgraded to 0.4.8

[dcchong]

dc-delegate upgraded to 0.4.8
bitsharesx-delegate upgraded to 0.4.8

please vote back

[king]

Thanks....  keep posting here and I'll vote you back in....

please vote me back

and Transfer to:
sun.delegate.service
moon.delegate.service

[xeroc]

mister               -> sun.delegate.service
delegate.mister  -> moon.delegate.service

Ui ... nice name

[king]

My delegate "mister" and "delegate.mister" has been upgraded to 0.4.8, but I hope I can replace the delegate account

mister               -> sun.delegate.service
delegate.mister  -> moon.delegate.service

[happyshares]

happyshares-2 upgraded to 0.4.8

[xeroc]

There is a bug in the fork handling code (or network code) that makes double producing blocks particularly harmful right now.  Anyone caught producing 2 blocks will be voted out until we have resolved the bug.

BM .. as an advice .. you should choose your words more wisely, because in general you are (or should) not be able to just "vote someone out" .. you can just remove *your* approval votes (which for sure weight a lot and I appreciate your weight on my delegates)

However, for outsides .. this 'sounds' like you could control the delegates .. and we have a centralized security scheme ...
just my 2bitusd

[CoinHoarder]

Updated to 0.4.8 yesterday btw

[bytemaster]

There is a bug in the fork handling code (or network code) that makes double producing blocks particularly harmful right now.  Anyone caught producing 2 blocks will be voted out until we have resolved the bug.

[bitwiz]

updated to 0.4.8, btw it's not producing blocks

[xeroc]

What's the reason is that? Sometimes when I upgrade the VPS client, I use Windows client to produce blocks temporarily, and there might be some overlap for a short while. I am wondering what's the consequence of doing that?

You produce a fork to the network as both clients produce TWO DIFFERENT blocks at the same time and broadcast them to the network

the delegate behind you has to decide for which one to take ...

in short: forks are bad .. and should be considered harmful

[ripplexiaoshan]

To All delegates:

Please do NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following

Code: [Select]

   c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.x              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.x              0       166 2014-08-26T14:44:10         1     N/A                  NO
We will strongly recommend others to vote them out.

What's the reason is that? Sometimes when I upgrade the VPS client, I use Windows client to produce blocks temporarily, and there might be some overlap for a short while. I am wondering what's the consequence of doing that? 

[DACSunlimited]

To All delegates:

Please do NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following

Code: [Select]

   c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.x              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.x              0       166 2014-08-26T14:44:10         1     N/A                  NO
We will strongly recommend others to vote them out.

[emski]

Angel and Lotto delegates were updated by the time of my first post in this thread.
Sorry for not explicitly mentioning that If that is the reason for down-voting them.

EDIT:
I saw that angel-delegate has signed 2 blocks. However it wasn't running on 2 instances.
The only time it was running on 2 instances was when my wallet was opened on secondary instance and it AUTOMATICALLY entered in block production mode.
However I stopped it in timely manner and I believe it didn't produce block. (cant be 100% sure though)

[wackou]

wackou-delegate upgraded to 0.4.8