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

Verification logic #6

Open
treyzania opened this issue Sep 15, 2017 · 0 comments
Open

Verification logic #6

treyzania opened this issue Sep 15, 2017 · 0 comments
Assignees
Milestone

Comments

@treyzania
Copy link
Contributor

treyzania commented Sep 15, 2017

Currently the model I have in mind for doing verification logic is to have a structure representing a "valid state" of the network. After that you can call functions on it that "extend" the state and attempt to include the object (a block or something) into the history. It'll return a Result<ValiationState, (ValidationState, ValidationError)> for the

Since this isn't a settlement platform we don't need to have a highly-time-dependent system like Bitcoin or another cryptocurrency has, so there is some local malleability we can and should tolerate, but not in the long term.

This is absolutely necessary for having a daemon that can talk to other nodes working properly (#5).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants