Maximilian Langenfeld
Maximilian Langenfeld
Currently, the sending of the Epoch decryption key-share by the keypers is triggered by receiving a gossipsub message `DecryptionTrigger` that functions as the collator-commitment. We still want to keep that...
### Problem If the keypers missed or ignored (e.g. message not valid *yet*) a collator's `DecryptionTrigger` message at some point, the system will not recover from this. The collator keeps...
To be checked for the current Eon before progressing batches in the batcher: - Eon public key exists in the DB - valid Keyper set exists in the DB In...
### Introduction Currently the `EonPublicKeyBroadcast` contract is not in use and [we don't seem to have agreed upon](https://github.com/shutter-network/rolling-shutter/issues/51) who should be the owner of that contract or how the public-keys...
- replace existing OpenAPI with JSON RPC API enpoints - `/ping` - `/next-epoch` - `/eon` - `/tx` with methods under the `shutter_` namespace. Eventually, use the `eth_sendRawTransaction` endpoint for the...
## Problem definition The shutter-transaction submission process has the following properties: - a user can submit transactions targeted for future batches up to a certain `BatchIndexAcceptanceInterval` threshold - the user...
Currently we do not distinguish the transaction types (EIP-2718) in the transaction handling and rely on accessing shutter-transaction specific fields like tx.BatchIndex(). This means that non-shutter-transactions (unencrypted tx's) will not...
Currently we only try to submit the batch transaction to the sequencer several times upon failure with a fixed retry interval. If that still fails, then the submittal will never...
When you configure incompatible TLS options, like setting `--https-address=:443 --force-https=true` without specifying `--tls-cert-file`, I encounter an unexpected error: ``` [2022/11/30 13:30:59] [main.go:60] ERROR: Failed to initialise OAuth2 Proxy: could not...