add security considerations to the introduction page

Author: anegg0

docs/pages/introduction.mdx

@@ -1,6 +1,6 @@
 # What is ZeroDev?
 
-ZeroDev is a programmable wallet infrastructure for teams building on EVM chains. It provides two things that work together: 
+ZeroDev is a programmable wallet infrastructure for teams building on EVM chains. It provides two things that work together:
 - A managed infrastructure layer — bundlers, paymasters, and the Kernel smart account contract
 - A set of SDKs that let you build ERC-4337 smart account features into your product without standing up or maintaining that infrastructure yourself.
 
@@ -12,17 +12,17 @@ If your team is deciding whether to build smart account capabilities in-house or
 
 ERC-4337 defines the protocol. It does not give you the stack.
 
-To ship a feature as simple as sponsored gas, you need a smart account contract, a paymaster, a bundler, a policy engine to control spending, and an SDK to connect it all to your frontend. Each of those pieces can be built independently — and teams do build them — but the integration work adds up fast. Bugs surface at the seams between components. Bundler reliability directly affects user-facing transaction success rates. Paymaster policy logic gets coupled into your backend and becomes a maintenance burden.
+To ship a feature as simple as sponsored gas, you need a smart account contract, a paymaster, a bundler, a policy engine to control spending, and an SDK to connect it all to your frontend. Each of those pieces can be built independently — and teams do build them — but the integration work adds up fast. Bugs surface at the seams between components, and in a smart account context those bugs carry real consequences: the account contract holds user funds, and a validation error in custom paymaster logic can cause transactions to be silently rejected by bundlers with no actionable error. Bundler reliability directly affects user-facing transaction success rates — custom bundler implementations often degrade under mempool congestion, producing the worst UX at exactly the moments when reliability matters most. Paymaster policy logic gets coupled into your backend and becomes a maintenance burden. The EntryPoint contract enforces strict simulation rules, so non-compliant UserOperations fail at submission rather than at execution, making root-cause analysis opaque even for experienced engineers.
 
-ZeroDev assembles this stack and operates it as a service. Kernel is the smart account contract: modular, audited, and one of the most deployed account implementations on Ethereum. The bundler and paymaster infrastructure runs across all major EVM chains. Gas policies are configured through a dashboard, not deployed as custom contracts. The SDKs handle the glue between your frontend and the protocol, at the level of abstraction that fits your architecture.
+ZeroDev assembles this stack and operates it as a service. Kernel is the smart account contract: modular, audited, and one of the most deployed account implementations on Ethereum — which means vulnerabilities have more surface area to be found and fixed before they affect your users. The bundler and paymaster infrastructure runs across all major EVM chains, tuned and monitored at scale with reliability tracked as a product metric. Gas policies are configured through a dashboard, not deployed as custom contracts. The SDKs handle the glue between your frontend and the protocol, at the level of abstraction that fits your architecture.
 
 ---
 
 ## build or buy?
 
-Building ERC-4337 infrastructure in-house is possible. It requires engineers who understand the EntryPoint contract, UserOperation lifecycle, paymaster validation rules, and bundler behavior under load — a specialized intersection of protocol knowledge and infrastructure engineering. Once built, it requires ongoing maintenance as the standard evolves and as you add chains.
+Building ERC-4337 infrastructure in-house is possible. It requires engineers who understand the EntryPoint contract, UserOperation lifecycle, paymaster validation rules, and bundler behavior under load — a specialized intersection of protocol knowledge and infrastructure engineering. Once built, it requires ongoing maintenance as the standard evolves (EntryPoint v0.7+, ERC-7702, and future spec changes) and as you add chains. A custom stack that falls behind on spec upgrades exposes users to compatibility gaps and potential fund-access issues. Security audits for a bespoke smart account contract are a per-team cost, repeated with every material change — and the contract itself is a direct custodian of user assets, where a single bug can mean irreversible loss of funds.
 
-ZeroDev is the buy answer for teams that want smart account capabilities without a dedicated protocol engineering function. The Kernel contract is open source and extensively audited. The infrastructure is shared across production deployments, which means reliability is a product priority, not a per-customer concern. Enterprise SLAs and support contracts are available for teams that need them.
+ZeroDev is the buy answer for teams that want smart account capabilities without a dedicated protocol engineering function. The Kernel contract is open source and extensively audited, with audit and security review costs shared across all users of the stack rather than borne by each team individually. The infrastructure is shared across production deployments, which means reliability is a product priority, not a per-customer concern. When the ERC-4337 spec evolves — new EntryPoint versions, ERC-7702 support — ZeroDev rolls out the upgrades so your team does not have to track and implement them. Enterprise SLAs and support contracts are available for teams that need them.
 
 For early-stage companies, adopting ZeroDev means shipping smart wallet features in days instead of months. For larger teams, it means redirecting protocol engineering capacity toward differentiated product work.
 
@@ -57,4 +57,3 @@ ZeroDev provides three SDKs, each calibrated to a different integration depth:
 Infrastructure concerns — bundler uptime, paymaster balance management, chain support — are handled by ZeroDev. Your team owns the integration; ZeroDev owns the ops.
 
 For teams evaluating integration scope before committing: each SDK has a working quickstart that covers the full round-trip (account creation, sponsored transaction, session key issuance) in under 50 lines of code.
-