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

Create a new keyper implementation for the generalized use of Shutter #551

Closed
6 tasks done
ylembachar opened this issue Nov 25, 2024 · 0 comments
Closed
6 tasks done

Comments

@ylembachar
Copy link
Contributor

ylembachar commented Nov 25, 2024

See EPIC shutter-network/shutter-api#1 for the full specification.

Create a new keyper implementation following the specification above for the MVP:

  • Listens to the registry contract for any new registrations
  • Monitors the time-based condition to release the keys / use block timestamp (first block with timestamp > to time)
  • In case of a downtime, release any keys that were supposed to be released during the downtime
  • Set a sent flag on any keys that were released to avoid sending them again
  • Endpoint to request old decryption keys should be open to the API to request old decryption keys if needed (already available in the keyper)
  • Custom implementation under keyperimpl
  • Deploy local keypers

Sub-issues:

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

1 participant