From 25ab27652cc76a4c7652d21ea679e1ec4b078c38 Mon Sep 17 00:00:00 2001 From: clawbot Date: Tue, 10 Mar 2026 10:49:04 -0700 Subject: [PATCH] fix: complete pow_token rename in README documentation Update 4 remaining references where the JSON field name was still 'hashcash' instead of 'pow_token' in README.md. --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 0668f9f..5965738 100644 --- a/README.md +++ b/README.md @@ -989,7 +989,7 @@ Create a new user session. This is the entry point for all clients. If the server requires hashcash proof-of-work (see [Hashcash Proof-of-Work](#hashcash-proof-of-work)), the client must include a -valid stamp in the `hashcash` field of the JSON request body. The required +valid stamp in the `pow_token` field of the JSON request body. The required difficulty is advertised via `GET /api/v1/server` in the `hashcash_bits` field. **Request Body:** @@ -1000,7 +1000,7 @@ difficulty is advertised via `GET /api/v1/server` in the `hashcash_bits` field. | Field | Type | Required | Constraints | |------------|--------|-------------|-------------| | `nick` | string | Yes | 1–32 characters, must be unique on the server | -| `hashcash` | string | Conditional | Hashcash stamp (required when server has `hashcash_bits` > 0) | +| `pow_token` | string | Conditional | Hashcash stamp (required when server has `hashcash_bits` > 0) | **Response:** `201 Created` ```json @@ -1022,7 +1022,7 @@ difficulty is advertised via `GET /api/v1/server` in the `hashcash_bits` field. | Status | Error | When | |--------|-------|------| | 400 | `nick must be 1-32 characters` | Empty or too-long nick | -| 402 | `hashcash proof-of-work required` | Missing `hashcash` field in request body when hashcash is enabled | +| 402 | `hashcash proof-of-work required` | Missing `pow_token` field in request body when hashcash is enabled | | 402 | `invalid hashcash stamp: ...` | Stamp fails validation (wrong bits, expired, reused, etc.) | | 409 | `nick already taken` | Another active session holds this nick | @@ -2132,7 +2132,7 @@ account registration, no IP-based rate limits that punish shared networks. 2. Client computes a hashcash stamp: find a counter value such that the SHA-256 hash of the stamp string has the required number of leading zero bits. -3. Client includes the stamp in the `hashcash` field of the JSON request body when creating +3. Client includes the stamp in the `pow_token` field of the JSON request body when creating a session: `POST /api/v1/session`. 4. Server validates the stamp: - Version is `1`