Revise blobs.md

sigp · Mar 11, 2024 · b9cd6c7 · b9cd6c7
1 parent 64ed3af
commit b9cd6c7
Showing 1 changed file with 7 additions and 3 deletions.
diff --git a/book/src/advanced-blobs.md b/book/src/advanced-blobs.md
@@ -11,10 +11,10 @@ In the Deneb network upgrade, one of the changes is the implementation of EIP-48
    One blob is 128 KB in size. Each block can carry a maximum of 6 blobs. Blobs will be kept for 4096 epochs and pruned afterwards. This means that the maximum increase in storage requirement will be:
 
    ```
-   128 KB / blob * 6 blobs / block * 32 blocks / epoch * 4096 epochs = 96 GB
+   2**17 bytes / blob * 6 blobs / block * 32 blocks / epoch * 4096 epochs = 96 GB
    ```
 
-   However, in practice, it is expected that not all blocks will be full of blobs. A practical scenario is that each block contains 3 blobs on average, which translates to an increase of storage requirement of 48 GB.
+   However, the blob base fee targets 3 blobs per block and it works similarly to how EIP-1559 operates in the Ethereum gas fee. Therefore, practically it is very likely to average to 3 blobs per blocks, which translates to an increase of storage requirement of 48 GB.
 
 
 1. Do I have to add any flags for blobs?
@@ -23,7 +23,11 @@ In the Deneb network upgrade, one of the changes is the implementation of EIP-48
 
 1. What if I want to keep all blobs?
 
-   Use the flag `--prune-blobs false` in the beacon node. Please note that this will keep all blobs and will thus require a high storage space. 
+   Use the flag `--prune-blobs false` in the beacon node. The storage requirement will be:
+
+   ```
+   2**17 bytes * 3 blobs / block * 7200 blocks / day * 30 days = 79GB / month or 948GB / year
+   ```
 
    To keep blobs for a custom period, you may use the flag `--blob-prune-margin-epochs <EPOCHS>` which keeps blobs for 4096+EPOCHS specified in the flag.