From b0107da216f722d7813d65305b507e0fa288027c Mon Sep 17 00:00:00 2001
From: user <user@Mac.lan guest wan>
Date: Tue, 10 Mar 2026 10:54:30 -0700
Subject: [PATCH] =?UTF-8?q?fix:=20rename=20hashcash=E2=86=92pow=5Ftoken=20?=
 =?UTF-8?q?JSON=20field=20reference=20in=20README?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 5965738..2f48e23 100644
--- a/README.md
+++ b/README.md
@@ -2189,7 +2189,7 @@ Both the embedded web SPA and the CLI client automatically handle hashcash:
 
 1. Fetch `GET /api/v1/server` to read `hashcash_bits`
 2. If `hashcash_bits > 0`, compute a valid stamp
-3. Include the stamp in the `hashcash` field of the JSON body on `POST /api/v1/session`
+3. Include the stamp in the `pow_token` field of the JSON body on `POST /api/v1/session`
 
 The web SPA uses the Web Crypto API (`crypto.subtle.digest`) for SHA-256
 computation with batched parallelism. The CLI client uses Go's `crypto/sha256`.