From 35a323ae3585c5e1e7599df07b0c89d4172473f0 Mon Sep 17 00:00:00 2001
From: 0xMattie <123201586+OPMattie@users.noreply.github.com>
Date: Fri, 7 Jun 2024 13:27:45 -0700
Subject: [PATCH] Update fp-changes.mdx

Updated viem update instructions
---
 pages/builders/notices/fp-changes.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/builders/notices/fp-changes.mdx b/pages/builders/notices/fp-changes.mdx
index a33025442..77fb1dcba 100644
--- a/pages/builders/notices/fp-changes.mdx
+++ b/pages/builders/notices/fp-changes.mdx
@@ -74,7 +74,7 @@ The proposed Fault Proof upgrade requires developers to enable Fault Proof chang
 
   *   **Option 1: Optimism SDK Update.** If you use OptimismSDK for bridging, simply update to version 3.2.0 or higher.
       The Optimism SDK changes do not break the API and require no changes other than updating to the correct software version to support the new `OptimismPortal` logic. The Optimism SDK will automatically begin to use the new logic once it detects that the FPM update has gone live.
-  *   **Option 2: Viem Update.** Viem changes will break the API and require both updating to latest version and replacing use of the currently used decorator with the `experimental` decorator that supports fault proofs. When Fault Proofs are on OP Mainnet, `publicActionsL2` will be updated to support fault proofs by default, and it will be recommended that developers switch to the stable API.
+  *   **Option 2: Viem Update.** Update to the latest version of Viem (version of >=2.9.0). Viem will automatically begin to use the new logic once it detects that the FPM update has gone live.
 
   ### Update Withdrawal Monitor