feat(docs): expand FDC Key Features list

Author: nikerzetic-aflabs

docs/fdc/1-overview.mdx

@@ -23,6 +23,9 @@ It allows users to submit attested data that smart contracts can trust, eliminat
 - **Easy Offchain Accessibility**: Data providers serve attestation responses and Merkle proofs offchain through a Data Availability (DA) Layer, ensuring efficient data retrieval.
 - **Proof-Based Verification**: Smart contracts validate Merkle proofs against the stored Merkle root, ensuring only authentic data triggers contract actions.
 - **Extensible Attestation Types**: New attestation types and data sources can be added through provider consensus, ensuring adaptability.
+- **Current State**: A proof can only be constructed for current states (transactions, API responses...), where a current state is a state no older than 14 days.
+- **Proof Availability**: Once the proof is constructed it remains available indefinitely.
+- **Security**: Although bitvoting information is public, it is insufficient to construct the Merkle proof without doing the verification work.
 
 ## Architecture
 
@@ -71,6 +74,8 @@ FDC currently supports seven attestation types, each serving specific verificati
 
 The first three attestation types are the most generally useful, while the last three are primarily used in **FAssets**.
 
+
+
 ## Workflow Overview
 
 For all attestation types, the workflow follows the same general steps.