mirror of
https://github.com/serai-dex/serai.git
synced 2024-12-26 21:50:26 +00:00
8b5eaa8092
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. |
||
|---|---|---|
| .. | ||
| coins | ||
| tests | ||
| coordinator.rs | ||
| db.rs | ||
| key_gen.rs | ||
| main.rs | ||
| plan.rs | ||
| scanner.rs | ||
| scheduler.rs | ||
| signer.rs | ||
| substrate_signer.rs | ||