If the validator did not perform his duty to include the transaction into the slot (either by misbehavbing or by missing a slot) the inclusion service must decrypt the scheduled encrypted transactions and send them to the public mempool.

The service must connect to the keypers' p2p network and listen on published decryption keys. Decryption keys are assigned to a slot. The service must later check if these transactions were included in the block for the corresponding slot.

Problem

Keypers release decryption keys for transactions and assign them to the next slot. When behaving correctly validators will only include those transactions which are assigned to their slot.
If a validator misses a slot (or misbehaves), the transactions might never be included into the chain. This would result in a very bad UX.

Solution

• The service listens to encrypted transactions

• The service listens to decryption keys

• The service decrypts the encryted data and retrieves the tx hash

• The service monitors the scheduled inclusion

• If a transaction is not included as planned

  • send transaction to the public mempool

  Issues

• #1
• #2
• #3

Encrypted transactions are sent to the Sequencer contract.

Encrypted transactions are published via emitting an TransactionSubmitted event. The service must keep track of these transactions.