My nodes appear to be rejecting the block 277935 that other nodes are trying to pass to it. It gives a bad signature message and bans that IP for 15 minutes or so. That would make me think that my block 277934 is different than the same block number everyone else has.
Your block 277934 is the same as ours. It is block 17565891496255612524, its timestamp is 32493681, and its signature is a31e0ae7a1e94c3175271157a43b6cd64eaff47825278bad28fdad6699f46f0147c3b2eea29fb7a
a8a0b90cdaf224ddf9e7afbf7d2de3a038b5ef25c87929fef
My node is stuck at height 279190, the one just after my transaction at 13:39:49 (GMT+2), similarly to your 277935. It advances some blocks, then it goes back, sometimes to the previous valid one 279189. I can not see other forgers when I am not forging. I restarted my node 2 hours ago, but it is the same (less peers now).
I told you to not forge, but with so few forgers I'm wrong. It is probably better now that all of us try to forge, and the NAS distributed system will decide. In fact, I created other accounts in order to distribute my forging power leasing smaller quantities to others. I can not do it until the network stabilize to one winner fork.
@User1397367406, I don't see you forging neither on my client nor on tiker's public client, are you not forging now?, or are you in yet another fork?