-
Notifications
You must be signed in to change notification settings - Fork 12
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
account-identity-proof-v1.md's novel signing preimage has no test vector, unlike every comparable novel-crypto construction in the repo
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#360 In marmot-protocol/marmot;group-state.md's repair-path option "import a verified current snapshot" is an undefined mechanism used exactly once
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#359 In marmot-protocol/marmot;agent-text-streams-quic.md's kind 1201/1202 JSON examples show fields (v, text, extra, sequence) that are never defined in prose
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#358 In marmot-protocol/marmot;layout.md applies a normative SHOULD to frozen, out-of-repo MIP documents that this repo cannot enforce
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#357 In marmot-protocol/marmot;nostr.md's kind 445 nonce-safety rationale rests on an unstated per-epoch message-count bound
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#356 In marmot-protocol/marmot;quic.md's certificate-pinning exception references an undefined "application's out-of-band watch configuration"
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#355 In marmot-protocol/marmot;agent-text-stream-quic-v1.md declares MarmotAgentTextStreamQuicRoleMaskV1 but never uses it — struct fields fall back to bare uint8
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#354 In marmot-protocol/marmot;group-messaging.md uses the implementation-layer term "callers," violating protocol-core's own no-local-implementation-names rule
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#353 In marmot-protocol/marmot;quic.md's endpoint candidate authority (host:port) has no maximum length bound, unlike nostr.md's relay URL profile
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#352 In marmot-protocol/marmot;account-identity-proof-v1.md's "this proof is not a Nostr event and is never published" is factually wrong if read as referring to the whole extension, not just the signing preimage
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#351 In marmot-protocol/marmot;convergence.md's branch-selection criterion 3 (higher raw_commit_depth) is mathematically unreachable given the effective_commit_depth formula
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#350 In marmot-protocol/marmot;group-profile-v1.md's "prior epoch" admin-check sentence is ambiguous about whether it covers proposal authorization, commit authorization, or both
specSpec inconsistency or claritySpec inconsistency or clarityStatus: Open.#349 In marmot-protocol/marmot;