From 91f99e90d3846fe21828eba4fc0f61e748935a15 Mon Sep 17 00:00:00 2001
From: jxom <7336481+jxom@users.noreply.github.com>
Date: Tue, 20 Jan 2026 14:51:07 +1100
Subject: [PATCH] docs: recommend reusing nonce keys

Ported from tempoxyz/tempo#2150
---
 src/snippets/tempo-tx-properties.mdx | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/src/snippets/tempo-tx-properties.mdx b/src/snippets/tempo-tx-properties.mdx
index 84ae809..82eabd6 100644
--- a/src/snippets/tempo-tx-properties.mdx
+++ b/src/snippets/tempo-tx-properties.mdx
@@ -444,6 +444,10 @@ in parallel without waiting for sequential nonce confirmation.
 By using different nonce keys, you can submit multiple transactions simultaneously that don't conflict with each other, 
 enabling parallel execution and significantly improved transaction throughput for high-activity accounts.
 
+:::warning
+**Reuse nonce keys instead of generating random ones.** Creating a new nonce key incurs a state creation cost that increases with the number of active keys (see [TIP-1000](/protocol/tips/tip-1000)). For most applications, using a small set of sequential nonce keys (e.g., `1n`, `2n`, `3n`) is sufficient and much more cost-effective than generating random nonce keys for each transaction.
+:::
+
 <div className="-mt-2" />
 
 <Tabs stateKey="library">
@@ -486,12 +490,12 @@ enabling parallel execution and significantly improved transaction throughput fo
 
     const hash1 = await client.sendTransaction({
       data: '0xdeadbeef0000000000000000000000000000000001',
-      nonceKey: 567n, // [!code hl]
+      nonceKey: 1n, // [!code hl]
       to: '0xcafebabecafebabecafebabecafebabecafebabe',
     })
     const hash2 = await client.sendTransaction({
       data: '0xdeadbeef0000000000000000000000000000000001',
-      nonceKey: 789n, // [!code hl]
+      nonceKey: 2n, // [!code hl]
       to: '0xcafebabecafebabecafebabecafebabecafebabe',
     })
     ```
@@ -546,12 +550,12 @@ enabling parallel execution and significantly improved transaction throughput fo
 
     sendTransaction({
       data: '0xdeadbeef0000000000000000000000000000000001',
-      nonceKey: 567n, // [!code hl]
+      nonceKey: 1n, // [!code hl]
       to: '0xcafebabecafebabecafebabecafebabecafebabe',
     })
     sendTransaction({
       data: '0xdeadbeef0000000000000000000000000000000001',
-      nonceKey: 789n, // [!code hl]
+      nonceKey: 2n, // [!code hl]
       to: '0xcafebabecafebabecafebabecafebabecafebabe',
     })
     ```