Distributed snapshutter setup

[ulope]

Release checklist

• add LICENSEs everywhere
• make https://github.com/shutter-network/snapshot-keyper public
• make https://github.com/shutter-network/rolling-shutter/pkgs/container/snapshot-main public
• make https://github.com/shutter-network/rolling-shutter/pkgs/container/snapshot-assets public
• tag release version for rolling-shutter repo
• tag release version for snapshot-main image
• Create genesis in distributed-snapshutter (see RELEASE.md)
• Collect keyper addresses from forum thread
• Ensure keyper set and collator in play.json for deployment is correct!
• deploy contracts from company owned key
• tag release snapshot-assets image
• update image versions in snapshot-keyper repository
• tag release version for snapshot-keyper repository
• Stop test keypers
• Clean/restart the seed nodes: update the genesis file on seed nodes
• Run bootstrapping/genesis keyper to start shuttermint chain
• Publish the release!

Questions

• How do the keyper configs get generated?
• Do we need to do anything about the public keys?

---

• multiple shuttermint nodes/production mode

---

• fix prometheus metrics
• store decryption key in snapshot db
• resend decryption keys on request

---

• test keyperset changes
• keyperset voting DKG
• active keyperset choice
• Make eon id offset configurable

---

#383

• third party keyper runtime setup
• seed node hosting
• on boarding documentation for keypers

---

Nice to haves:

• multiple(?)/failover safe "snapshot hubs"
• failover for snapshot command/interface
• authenticate jsonrpc requests (+"responses"?)

---

• switchover solution for new snapshot deployment

[LoringHarkness]

I'm updating the OKRs for Q4 2024, and this is one of them.
Which milestone(s) / tasks above are we aiming to reach / complete by end of October?