docs: refresh rust-nostr NIP-46 compat note + link filed upstream issue#56
Open
DocNR wants to merge 1 commit into
Open
docs: refresh rust-nostr NIP-46 compat note + link filed upstream issue#56DocNR wants to merge 1 commit into
DocNR wants to merge 1 commit into
Conversation
The rust-nostr family note was stale (dated 2026-04-22, "not yet filed"). Updated it with the verified state of rust-nostr master 0a030e1c7: the response parser and the nostrconnect:// path now accept the echoed-secret connect response, but the bunker:// path (connect() -> to_ack()) still rejects it. Also documents the swapped expected/received labels in the UnexpectedResponse Display impl. Filed upstream as rust-nostr/nostr#1352 and linked it in the open-upstream-issues table. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/nip46-compatibility.mdwith the verified state of rust-nostr master0a030e1c7— the response parser and thenostrconnect://path now accept the echoed-secret connect response, but thebunker://connect()path still rejects it viares.to_ack()?.Error::UnexpectedResponse'sDisplayimpl.Last updateddate + changelog.Context
A Flare iOS user reported a
bunker://pairing failure that looked like a Clave spec violation. It's actually a rust-nostr bug (Flare usesnostr-sdk-kmp, which fully delegates NIP-46 to rust-nostr): rust-nostr'sbunker://connect path rejects the spec-allowed echoed-secret response. Clave's behavior is NIP-46 compliant and unchanged — this PR is docs-only.Test plan
🤖 Generated with Claude Code