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

Cache SpendProviderOutput at incentive service, send it periodically to the DS protection service #68

Open
pschuermann97 opened this issue Nov 17, 2021 · 2 comments
Labels
enhancement Improve some existing feature/code

Comments

@pschuermann97
Copy link
Collaborator

At the moment, the deduct service sends every observed transaction to the deduct service immediately.
To provide actual offline double-spending protection, we need a cache for the observed transaction data which is periodically transferred to the double-spending protection database.

@this-kramer this-kramer added the enhancement Improve some existing feature/code label Mar 24, 2022
@this-kramer
Copy link
Member

Maybe rename this to something like Cache SpendProviderOutput at incentive service, send it periodically to the DS protection service

@pschuermann97 pschuermann97 changed the title Implement offline double-spending protection Cache SpendProviderOutput at incentive service, send it periodically to the DS protection service Jul 20, 2022
@pschuermann97
Copy link
Collaborator Author

pschuermann97 commented Jul 28, 2022

Agreement meeting 28.7.22: this is rather annoying for demonstration purposes (introduces artificial delay), we should just write a short remark into paper that our system supports this type of offline doublespending protection and the implementation is just a technical, not a mathematical/conceptual problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improve some existing feature/code
Projects
None yet
Development

No branches or pull requests

2 participants