[DA Footprint Limit] Documentation

[geoknee]

• Should emphasize the risks around setting the scalar
  • too high (excludes too much traffic)
  • too low (ineffective at protecting against spam or DA backlogs, throttling becomes likely)
• When Gas Limit is changed, the effective DA footprint block limit scales proportionally by design. So in general it is fine not to change the scalar when changing the gas limit, but if the absolute limit should stay the same, the scalar needs to be increased.
• If no limit is set, or the value 0 is set (again) for the daFootprintGasScalar at the SystemConfig, a default value of 400 is used.
• If the feature should be disabled, set the scalar to a very low value, like 1.

---

• Jovian: DA footprint block limit design-docs#317 design doc (but describes old design using the gasLimit max instead of blobGasUsed for the DA footprint)
• Specs
• https://miro.com/app/board/uXjVJIlXd1Q=/ threat modelling

[geoknee]

This issue could be tracked at the same time [DOCS] Begin documenting MinBaseFee feature docs#1710. It's pretty self explanatory.