What If 2 players resign at the same time?

I did read somewhere it results in a draw, though it has never happened as far as I know.

@DeadlyKillerInstinct said in #11:

I did read somewhere it results in a draw, though it has never happened as far as I know.

Really?

Online one resignation will always be processed before the other, as people have written above. The first one to be processed should take effect. The second will be rejected because the game is over.

Over-the-board I am not aware of any rule about a draw. But are you thinking of the rule, quite a new one, in the FIDE laws that it s a draw if you resign in a position where there is no legal sequence of move where you can be mated? That's just lately become the rule for OTB play but Lichess hasn't implemented it, as confirmed by the following game played a week ago:

The next time someone pointlessly asks if they can be a GM, a great answer would be..

“You’ve less chance than two people resigning at the same time.!”

@BorisOspasky To paraphrase some rapper " I got 99 problems but simultaneous chess resignations ain't one of 'em."

i love pointless threads and guessing about things I know nothing about.

@Resurr3ction said in #4:

I have very little knowledge about data transfer but I am very sure that two resignations at the same time are technically not possible because the incoming data/information is always one after another. Same with outgoing data from one router if two players are on the same local network for example.

that's a great point, with one ethernet cable, the server receives one frame at a time, but, as the data travels up the network stack to the application layer there could be opportunities for parallel processing, delays, things getting out of order. also, that's assuming one server. things get more complicated when an application runs on many servers.

I have the same guess that it's not possible, but, I wouldn't be surprised if there was a tiny tiny chance of the second resignation on the ethernet cable being seen first by the application.

@h2b2 You could have a similar problem if one player accepts a draw offer while the other resigns "at the same time".

@h2b2 said in #15:

I wouldn't be surprised if there was a tiny tiny chance of the second resignation on the ethernet cable being seen first by the application
Not so tiny, actually. Most enterprise network cards have the incoming packets spread over multiple queues which are usually processed on different CPUs so that reorderings are quite common. Which is also one of the reasons why we want packets from the same TCP connection to be directed to the same queue (and CPU) because otherwise the reordering would harm the performance a lot.

That being said, the differences in how long it takes for packets from different clients to reach the server over Internet play much bigger role. And, more important, whatever the processing looks like in different layers, the events related to a particular game need to be serialized eventually.

What if they both checkmated each other at the same time? That would be fun.

Imagine all those misdelivered packets being ripped open.. the cpu would probably melt and the network would collapse and Lichess would cease to function.

The up side of that is there’d be no more utterly pointless off topic threads.

Send the guy that owns Lichess shopping at PC World for some better CPUs just in case.

@spindriftdrinker He could stream a few rapping tracks to make the experience more enjoyable.

i expect thibault will whine..