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

Backup operation sets #40

Closed
adamstallard opened this issue Dec 13, 2018 · 4 comments
Closed

Backup operation sets #40

adamstallard opened this issue Dec 13, 2018 · 4 comments
Assignees

Comments

@adamstallard
Copy link
Member

adamstallard commented Dec 13, 2018

related to #38

@adamstallard
Copy link
Member Author

This could be used as an incremental backup to replay operations after a database dump is restored.

@adamstallard adamstallard changed the title Backup operation sets into larger offline operation set Backup operation sets Jun 25, 2019
@adamstallard
Copy link
Member Author

Backed up operation sets should have an accompanying file with signatures from all nodes that endorse the operation set.

@abramsymons
Copy link
Collaborator

abramsymons commented Jan 27, 2020

We have a collection for operations on the nodes.
We can backup operations in the predefined periods that we use for getting snapshot from the system for scorer, and clear operations for example older than one day.
What should we do with these backup of operations (operation sets)? can you explain more about this please @adamstallard :

Backed up operation sets should have an accompanying file with signatures from all nodes that endorse the operation set.

@abramsymons abramsymons self-assigned this Jan 27, 2020
@adamstallard
Copy link
Member Author

adamstallard commented Jan 27, 2020

We have a collection for operations on the nodes.
We can backup operations in the predefined periods that we use for getting snapshot from the system for scorer, and clear operations for example older than one day.
What should we do with these backup of operations (operation sets)? can you explain more about this please @adamstallard :

Backed up operation sets should have an accompanying file with signatures from all nodes that endorse the operation set.

What I mean is that when you publish a backup file you can also publish another file that has the hash of the file to use a checksum, then in the same file with the hash, the node can provide a signature of that checksum that it signed with its private key so that anyone can verify that the node has endorsed that backup file.

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

No branches or pull requests

2 participants