silentmode/WizardConnect
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Accept change

Browse source
This commit is contained in:
Jakob Notland 2026-04-21 14:10:33 +02:00
parent 318d97439f
commit cdd357cb08
1 changed files with 15 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
packages/core/src/relay-client.ts
View file

@ -26,12 +26,19 @@ import { ChunkAssembler } from "./chunk-assembler.js";
import { debug, error as logError, Scope } from "./log.js"; import { debug, error as logError, Scope } from "./log.js";
/// Messages larger than this (JSON chars) are split into chunks when the peer /// Messages larger than this (JSON chars) are split into chunks when the peer
/// supports chunking. Chosen conservatively: a 30 000-char message produces a /// supports chunking. The NIP-44 limit is 65 535 bytes of plaintext per call.
/// rumor JSON of ≈32 700 chars after NIP-59 double-encoding, well under the /// createWrap encrypts the seal JSON; that seal JSON contains the base64 of the
/// ~40 960-char threshold at which the outer NIP-44 layer would fail. /// inner NIP-44 ciphertext. NIP-44 pads plaintext to the next power of two, so
/// the ciphertext size jumps sharply once the rumor JSON crosses 32 768 bytes:
/// rumor JSON ≤ 32 768 B → inner ciphertext ≈ 43 780 B (base64) → seal JSON
/// ≈ 44 130 B → safe. Rumor JSON > 32 768 B → inner ciphertext ≈ 87 472 B
/// → seal JSON ≈ 87 822 B → exceeds the 65 535-byte limit → NIP-44 throws.
/// A 30 000-char message produces a rumor JSON of ≈ 30 300 bytes, leaving a
/// comfortable 2 500-byte margin below the 32 768-byte cliff.
const MAX_SAFE_MESSAGE_SIZE = 30_000; const MAX_SAFE_MESSAGE_SIZE = 30_000;
/// Size of each chunk_data slice (chars). Kept below MAX_SAFE_MESSAGE_SIZE so /// Size of each chunk_data slice (chars). A 28 000-char slice produces a chunk
/// JSON of ≈ 28 100 bytes, which sits safely below MAX_SAFE_MESSAGE_SIZE so
/// chunk metadata overhead cannot push a fragment over the limit. /// chunk metadata overhead cannot push a fragment over the limit.
const CHUNK_SIZE = 28_000; const CHUNK_SIZE = 28_000;
@ -209,6 +216,7 @@ export class RelayClient extends EventEmitter {
async disconnect(): Promise<void> { async disconnect(): Promise<void> {
this.lastProcessedTimestamp = Math.floor(Date.now() / 1000); this.lastProcessedTimestamp = Math.floor(Date.now() / 1000);
this.messageQueue.setNotReady(); this.messageQueue.setNotReady();
this.peerSupportsChunking = false;
if (this.readyTimeoutId) { if (this.readyTimeoutId) {
clearTimeout(this.readyTimeoutId); clearTimeout(this.readyTimeoutId);
@ -235,9 +243,9 @@ export class RelayClient extends EventEmitter {
/** /**
* Notify the RelayClient that the connected peer supports chunked messages. * Notify the RelayClient that the connected peer supports chunked messages.
* Must be called after receiving a wallet_ready (or equivalent) that includes * Call this after receiving a wallet_ready that includes the "chunked_messages"
* the "chunked_messages" extension. Resets to false on every new connection * extension. Automatically reset to false by disconnect() — call again on
* cycle implicitly — callers should set it again on each wallet_ready. * each wallet_ready so reconnects don't inherit stale state.
*/ */
setPeerSupportsChunking(supports: boolean): void { setPeerSupportsChunking(supports: boolean): void {
this.peerSupportsChunking = supports; this.peerSupportsChunking = supports;