Update rollup-vs-validium.md

Added a note clarifying that EIP4844 is not actually supported in the CDK at this time.

Author: Swader

docs/cdk/concepts/rollup-vs-validium.md

@@ -10,7 +10,9 @@ Using Ethereum to store transaction data is generally considered the most secure
 
 Within the rollup category, there are further nuances to storing transaction data on Ethereum. Some rollups post serialized transaction data directly, whereas others post state differences instead. Some rollups use [calldata](https://docs.soliditylang.org/en/v0.8.26/types.html#data-location) to store transaction data, while others use more recent Ethereum features such as Blobs, introduced in [EIP-4844](https://www.eip4844.com/).
 
-The CDK provides full flexibility to developers to choose what to do with transaction data, including the ability to build rollups that store data on Ethereum as a rollup like the Polygon zkEVM.
+The CDK provides full flexibility to developers to choose what to do with transaction data, including the ability to build rollups that store data on Ethereum as a rollup like the Polygon zkEVM. 
+
+Note: Currently, the rollup mode of Polygon CDK does not support BLOB mode (EIP4844), but this functionality is coming soon.
 
 ## Validiums
 
@@ -61,4 +63,4 @@ Below is a breakdown of the technical differences between a zkEVM rollup and val
 ## Further reading
 
 - [Ethereum documentation: rollups](https://ethereum.org/en/developers/docs/scaling/#rollups)
-- [Ethereum documentation: validiums](https://ethereum.org/en/developers/docs/scaling/validium/)
+- [Ethereum documentation: validiums](https://ethereum.org/en/developers/docs/scaling/validium/)