Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Desync Validation: State consistency validation between peers #20

Open
lucasteles opened this issue Mar 20, 2024 · 0 comments
Open

Desync Validation: State consistency validation between peers #20

lucasteles opened this issue Mar 20, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@lucasteles
Copy link
Owner

lucasteles commented Mar 20, 2024

It is hard to know if two client states are correct.

We need at least periodic messages with the frame number and state checksum to be verified by other peers.

If the validation fails, the client should be disconnected.

UPDATE:
There is a started work on consistency-check branch.

The problem is, that the GetHashCode() approach for state validity it is not stable between different appdomains because it changes on every execution, so it necessary to rethink how we do checksum, and/or even how we are serializing the state data as most eligible checksum algorithm run on byte arrays (like Fletcher-32, CRC, etc).

@lucasteles lucasteles added the enhancement New feature or request label Mar 20, 2024
@lucasteles lucasteles self-assigned this Mar 25, 2024
@lucasteles lucasteles changed the title State consistency check udp message Desync Validation: State consistency validation between peers Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant