From b140f25cbeec3e120df4f1fbc3b6850683a8cb91 Mon Sep 17 00:00:00 2001
From: 0xchainer <109617724+0xchainer@users.noreply.github.com>
Date: Sun, 24 May 2026 23:46:29 +0300
Subject: [PATCH] fix(docs): add .slice(2) to dataSuffix hex stripping in
 builder codes examples

---
 tmp-builder-codes-outline.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tmp-builder-codes-outline.mdx b/tmp-builder-codes-outline.mdx
index 60a9c818c..069cea611 100644
--- a/tmp-builder-codes-outline.mdx
+++ b/tmp-builder-codes-outline.mdx
@@ -16,13 +16,13 @@ You do **not** build, validate, or encode anything — you just use the suffix w
 
 If your app sends a normal `eth_sendTransaction`:
 
-`tx.data = tx.data + dataSuffix;`
+`tx.data = tx.data + dataSuffix.slice(2);`
 
 ### **B. Smart Account / ERC-4337 UserOps**
 
 If your app constructs User Operations:
 
-`userOp.callData = userOp.callData + dataSuffix;`
+`userOp.callData = userOp.callData + dataSuffix.slice(2);`
 
 Smart accounts require putting the suffix inside the `callData` of the userOp.