Luke Parker 8b5eaa8092 Add additional checks to key_gen/sign ...

There is the ability to cause state bloat by flooding Tributary.
KeyGen/Sign specifically shouldn't allow bloat since we check the
commitments/preprocesses/shares for validity. Accordingly, any invalid data
(such as bloat) should be detected.

It was posssible to place bloat after the valid data. Doing so would be
considered a valid KeyGen/Sign message, yet could add up to 50k kB per sign.

2023-04-20 05:36:48 -04:00

..

coins

Code a method to determine the activation block before any block has consensus

2023-04-18 03:04:52 -04:00

tests

Code a method to determine the activation block before any block has consensus

2023-04-18 03:04:52 -04:00

coordinator.rs

Finish routing eventualities

2023-04-11 05:49:27 -04:00

db.rs

Use a single txn for an entire coordinator message

2023-04-17 23:55:12 -04:00

key_gen.rs

Add additional checks to key_gen/sign

2023-04-20 05:36:48 -04:00

main.rs

Code a method to determine the activation block before any block has consensus

2023-04-18 03:04:52 -04:00

plan.rs

Processor (#259)

2023-03-16 22:59:40 -04:00

scanner.rs

Clarify safety of Scanner::block_number and KeyGen::keys

2023-04-18 00:26:19 -04:00

scheduler.rs

Merge AckBlock with Burns

2023-04-15 18:38:40 -04:00

signer.rs

Add additional checks to key_gen/sign

2023-04-20 05:36:48 -04:00

substrate_signer.rs

Use a single txn for an entire coordinator message

2023-04-17 23:55:12 -04:00