Update SLA and add message size estimator (#216)

Co-authored-by: Robert Raynor <[email protected]>

docs/eigenda/operator-guides/requirements/protocol-SLA.md

@@ -70,10 +70,13 @@ Operators are required to maintain high availability of both attesting and servi
 | --- | --- | --- |
 | Baseline | 90 % | 2.4 hours |
 | > 5%  | 95% | 1.2 hours | 
-| > 10% | 97.5% | 36 minutes |
+| > 10% | 98% | 29 minutes |
+| > 15% | 99.5% | 7 minutes |
 
 Operators who hold delegated stake in multiple quorums must satisfy the SLA associated with each of their registered quorums. For instance, an operator holding 1% of stake in 'quorum 0' and 7% of stake in 'quorum 1' must keep its signing rate and serving availability above 90% for 'quorum 0' and 95% for 'quorum 1'. 
 
+
+
 **Enforcement Actions**
 
 Operators can be subject to forced ejection from the protocol if they fail to meet their Rolling Daily SLA. This action can occur with or without prior notice and may follow initial soft enforcement steps, including the disclosure of the operator's SLI and overall ranking. Ejection is performed on a per quorum basis.  An operator holding a 10% stake in 'quorum 0' who does not attest to blobs for 45 minutes may face immediate ejection from that quorum, particularly if their performance compromises the network's liveness.

docs/eigenda/operator-guides/requirements/system-requirements.md

@@ -50,6 +50,17 @@ The following table summarizes required storage capacity based on TQS:
 | Up to 10%                      | 25 Mbps              | 4 TB             |
 | Up to 20%                      | 50 Mbps              | 8 TB             |
 
+
+:::info
+The rough size of the message sent from the EigenDA disperser to a DA node can be estimated using the following formula: 
+
+```
+<batch size (MB)>  = <throughput (MB/s)>  * <batch interval (s)>  * <coding rate> * <% stake>
+```
+
+Where `<coding rate> = 5` for all current EigenDA quorums. So if the network is operating at 1MB/s with a 10 minute batch interval, and a node has 5% of the stake, then that node will receive roughly 150MB per message from the disperser. 
+:::
+
 ## System Upgrades
 
 Since system requirements scale dynamically in accordance with the amount of stake delegated to the operator, node operators may from time to time need to upgrade their system setups in order to continue meeting the [Protocol SLA](./protocol-SLA/). Guidance for performing such upgrades is covered in [System Upgrades](../upgrades/software-upgrades/)