HIGH: Lock the DB for the same socket while verifying self to avoid glitching

[TLTimeplex]

Is your feature request related to a problem? Please describe.
Possible glitch where a user sends first a verification and then a public key without waiting for the respnse, so that he would be overrideing the pub key and would now have stollen the acount. Still he would not be able to read any chats but he has kicked out the owner from its acounr and can now be someone else.

Describe the solution you'd like
Add a bool or a lockable object to the socket to lock the entrance to the DB or the execution of anouther request.