ylembachar
ylembachar
**Description** The keyper panics during validator registry sync when a registration event results in an empty pubKeys slice. This seems to occur when syncing from older block heights and seems...
Currently, enabling the decryption key HTTP endpoint (e.g., for /decryption-key) also enables other sensitive admin endpoints such as /shutdown and /trigger-decryption. This poses a risk when asking decentralized keypers to...
Reference: https://github.com/libp2p/go-libp2p/issues/3287
We want to expose and track which Execution Layer (EL) and Consensus Layer (CL) clients each keyper instance is using to improve observability across the network.
- [x] Fix the synch monitor in the Gnosis keyper following the updates made in issue [582](https://github.com/shutter-network/rolling-shutter/issues/582) - [x] Refactor the code to use the same package to avoid duplicating...
Fix the table constraint issue that prevents registering multiple validators in a single event.
**Rename & Archive Old Repositories** - [ ] Rename shutter repo → shutter-crypto. - [ ] Extract shlib into its own repository. - [ ] Rename rolling-shutter to shutter /...
- Update the DB to collect the registration events and store them under the keyper implementation DB - Add a flag to each event that indicates whether decryption key shares...
Create basic keyper implementation that inherits the core keyper functionality and that will serve as the backbone for the shutter service implementation
Features: - Event-based decryption triggers in: https://github.com/shutter-network/rolling-shutter/issues/631 - Allow keys message with no signature and remove current decryption trigger validation in https://github.com/shutter-network/rolling-shutter/issues/620 - Add compatibility for previous eons in https://github.com/shutter-network/rolling-shutter/pull/624...