You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Maybe rename this to something like Cache SpendProviderOutput at incentive service, send it periodically to the DS protection service
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
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
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.
The text was updated successfully, but these errors were encountered: