From 804ce76c167d0f435cbff65e7e3f4aad720915f6 Mon Sep 17 00:00:00 2001 From: ss-core-02 Date: Wed, 26 Aug 2026 09:50:38 -0700 Subject: [PATCH] docs(agent-broker): require public keys to be valid x-only points Review on the contract asked the pubkey type to preserve the public-key invariant rather than accept any 64 hex characters; the contract is being tightened to match, so the spec states the rule. Co-authored-by: Bradley Axen Signed-off-by: Bradley Axen --- docs/agent-broker.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/agent-broker.md b/docs/agent-broker.md index a821d520b0..d4a3d00852 100644 --- a/docs/agent-broker.md +++ b/docs/agent-broker.md @@ -210,7 +210,9 @@ value is canonical whether it was constructed or parsed: sender may use uppercase, the unhyphenated 32-character form, braces, or a `urn:uuid:` prefix and will be read as having sent the canonical form. - A **public key**, **event id**, or **d-tag** is 64 hex characters. Canonical - form is lowercase. + form is lowercase. A public key must additionally be a valid secp256k1 + x-only point — 64 hex characters that name no point on the curve are + malformed, not merely useless. Without this, a caller's spelling of a channel and `H`'s canonical echo of the same channel would fail I5's correlation check for a correct answer. The