Constellation members validation

[orbitlens]

Constellation members (regardless whether its Alpha or auditor) should force close incoming connection in case if:

Constellation member connection

• Node public key doesn't belong to a known Alpha or auditor member.
• Other party repeatedly sends invalid data: invalid messages format, invalid signatures, malformed requests, invalid apex numbers, etc.
• Network connection problems detected: no keep-alive response, repeatedly failing WebSocket connection or multiple lost messages.
• Auditors always refuse any incoming connections.

Client connection

• Client doesn't have an account in this constellation (client should wait until the deposit is processed).
• Client closed an account – all funds withdrawn.
• Client with the same public key is logged in from another device (we should lift this restriction in the future versions).
• Client repeatedly intentionally violates constellation limits: too many requests per seconds, inconsistent or malformed quantum requests, concurrent withdrawal requests.
• Network connection problems detected: no keep-alive response, repeatedly failing WebSocket connection or multiple lost messages.