Skip to content

Commit 00bdbe5

Browse files
committed
add FM7
1 parent a6c13c8 commit 00bdbe5

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

Diff for: security/fma-supervisor.md

+16
Original file line numberDiff line numberDiff line change
@@ -227,6 +227,22 @@ And all Failure Modes are some subtype. Incorrect responses are much worse than
227227
- Mitigation
228228
- Standard Mode could allow for *multiple* Supervisor Endpoints to be specified, they could confirm that all endpoints agree, preventing dishonesty from one party from deceiving the Node.
229229

230+
## FM7: Supervisor Indexing Fills Disk
231+
- Description
232+
- The Supervisor indexes information about every log in interoperating chains.
233+
- Each log takes at least 24 bytes to store, with Executing Messages taking 3x as much.
234+
- A large network like OPM processes millions of logs per day.
235+
- If not provisioned correctly, the Supervisor may run out of room to store the DB.
236+
- Should this occur, the Supervisor will fail in indeterminite ways and will likely crash, leading to liveness failures.
237+
- Risk Assessment
238+
- Low Impact, Low Likelihood
239+
- We can monitor disk space and keep machines well provisioned.
240+
- Supervisor already holds a very minimal amount of data per log, costing ~134Mb per chain per day.
241+
- Mitigations
242+
- The Supervisor may not need to hold old data if logs past a certain age can't be referenced.
243+
- Excessively old data could be purged from the DB and obtained through some alternative implementation,
244+
if the caller still needed it.
245+
230246
# Action Item Summary
231247

232248
Across all these Failure Modes, the following are explicitly identified improvements and mitigations we should make soon:

0 commit comments

Comments
 (0)