feat: add 4337 dependency to spec

standard/ERCs/erc-6900.md

@@ -586,6 +586,19 @@ ERC-4337 compatible accounts must implement the `IAccount` interface, which cons
 
 This proposal includes several interfaces that build on ERC-4337. First, we standardize a set of modular functions that allow smart contract developers greater flexibility in bundling validation, execution, and hook logic. We also propose interfaces that provide methods for querying execution functions, validation functions, and hooks on a modular account. The rest of the interfaces describe a module's methods for exposing its modular functions and desired configuration, and the modular account's methods for installing and removing modules and allowing execution across modules and external addresses.
 
+### ERC 4337 Dependency
+
+ERC 6900's main objective is to create a secure and interoperable foundation through modular modules to increase the velocity and security of the Smart Account ecosystem and ultimately the wallet ecosystem.
+Currently, the ERC 6900 standard enforces the ERC 4337 for the validation and execution, however, this does not dictate that ERC 6900 will continue to be tied to the ERC 4337.
+It is likely that smart account builders will want to develop modular accounts that do not use ERC 4337 in the future, e.g., Native AA on rollups.
+Moreover, it is expected that the version of EntryPoint contract will continue to evolve until there is a protocol-level account abstraction.
+
+ERC 6900, having the objective to provide the secure foundation for modular smart account layer, does not try to be tied with a specific version of continuously evolving EntryPoint and AA architecture but rather position to function as a modular layer encompassing them.
+
+To be in line with this, identical behavior and functions will exist for EntryPoint v6 with `UserOperation` and will continue to exist when a new EntryPoint version comes out with a different UserOp structure.
+
+ERC 6900 could evolve with ERC 4337 becoming an extension through a separate ERC for 6900 if more builders build on a new architecture, but in its current state, it enforces ERC 4337 within the standard, considering that the vast majority of smart accounts utilize ERC 4337.
+
 ## Backwards Compatibility
 
 Existing accounts that are deployed as proxies may have the ability to upgrade account implementations to one that supports this standard for modularity. Depending on implementation logic, existing modules may be wrapped in an adapter contract to adhere to the standard.