OptionalautoCompress?: booleanOptionalbz2?: Bzip2Injected bz2 module; never imported by the library.
Optionaldata?: Uint8Array<ArrayBufferLike>Sender-side payload.
OptionalisRequest?: booleanThis Resource is a REQUEST body.
OptionalisResponse?: booleanThis Resource is a RESPONSE body.
Optionallink?: LinkOptionaloriginalHash?: Uint8Array<ArrayBufferLike>OptionalrequestId?: Uint8Array<ArrayBufferLike>Associated REQUEST id (§11).
Whether sender preparation is done.
Outstanding part requests in the current window (receiver).
Receiver request window during a transfer.
StaticDEFAULT_Cap on advertised transfer/logical size at accept time (§10.4 bomb defense).
StaticHASHMAP_Constants in the advertisement-size formula HASHMAP_MAX_LEN = (MDU-134)/4.
StaticHEADER_RNS.Packet.HEADER_MAXSIZE — worst-case header after relay HEADER_1→HEADER_2
conversion: flags(1) + hops(1) + transport_id(16) + dest_hash(16) + context(1).
StaticIFAC_RNS.Reticulum.IFAC_MIN_SIZE — reserved IFAC bytes when computing SDU.
StaticRANDOM_Size of the throwaway random prefix prepended to the wire body (§10.2
step 3). Distinct from the advertisement r field.
StaticWINDOWInitial receiver request window (§10.10).
StaticWINDOW_Default window cap used for the collision-guard span (§10.10 WINDOW_MAX_SLOW).
Collision-guard span (§10.2 step 7): map_hashes must be unique within this many parts of any position.
Number of 4-byte map_hashes that fit in one advertisement's m field
(§10.4): floor((link.mdu - 134) / 4). At the default MDU 431 this is 74.
Maximum part body size. Parts are raw slices of the already-encrypted
whole, sent as context=RESOURCE packets which are NOT token-encrypted
(§10.6 gotcha), so the full SDU is available for part data.
The addEventListener() method of the EventTarget interface sets up a function that will be called whenever the specified event is delivered to the target.
Optionaloptions: boolean | AddEventListenerOptionsBuilds and sends the RESOURCE_ADV (§10.4). The link registers this
resource as an outgoing transfer keyed by hash.
Receiver: assembles all parts, link-decrypts, strips the prefix, optional decompress, recomputes the integrity hash, and emits the RESOURCE_PRF (§10.8).
Cancels the resource. Sender emits RESOURCE_ICL; receiver cancels locally (an ordinary receiver cancel does NOT emit RESOURCE_RCL per §10.9).
The dispatchEvent() method of the EventTarget sends an Event to the object, (synchronously) invoking the affected event listeners in the appropriate order. The normal event processing rules (including the capturing and optional bubbling phase) also apply to events dispatched manually with dispatchEvent().
Current transfer progress as a float in [0.0, 1.0].
Receiver: peer (initiator) cancelled via RESOURCE_ICL.
Sender: peer (receiver) rejected via RESOURCE_RCL.
Sender: fulfils an inbound RESOURCE_REQ (§10.5/§10.7) — emits the requested RESOURCE part packets, and a RESOURCE_HMU continuation when the receiver signalled hashmap exhaustion.
Receiver: applies a RESOURCE_HMU hashmap continuation (§10.7).
Receiver: places an incoming RESOURCE part by matching its 4-byte map_hash against the hashmap (§10.6). Returns true if the part was placed.
The removeEventListener() method of the EventTarget interface removes an event listener previously registered with EventTarget.addEventListener() from the target. The event listener to be removed is identified using a combination of the event type, the event listener function itself, and various optional options that may affect the matching process; see Matching event listeners for removal.
Optionaloptions: boolean | EventListenerOptionsReceiver: builds and sends the next RESOURCE_REQ for missing parts
(§10.5). Windowed stop-and-wait for Phase 2 — requests up to window
outstanding missing parts, then waits for them before requesting more.
Sender: validates a RESOURCE_PRF (§10.8). Body is resource_hash(32) || full_proof(32); full_proof must equal the pre-computed expected_proof.
Resolves when the transfer reaches a terminal state (COMPLETE/FAILED/etc). Rejects if the resource fails rather than completing.
Staticaccept
A Reticulum Resource — a fragmented transfer riding on top of an ACTIVE Link.
Construct with
datafor the sender side (thenawait resource.advertise()); or via Resource.accept on the receiver side. Both sides emitprogress/complete/failedevents, and exposewhenComplete()for promise-based consumers.