Tags: paritytech/smoldot
Tags
npm smoldot v3.4.0 (#3333) This is to: - publish `smoldot-v3.4.0` npm. - publish crates `smoldot-light v2.0.0`, `smoldot v2.2.0` ## Changes ### Added - Implement the [RFC-0163](https://github.com/polkadot-fellows/RFCs/blob/main/text/0163-ec-host-functions.md) elliptic curve host functions: scalar multiplication and multi-scalar multiplication on bandersnatch (`ed_on_bls12_381_bandersnatch`), and scalar multiplication, multi-scalar multiplication, multi Miller loop and final exponentiation on BLS12-381. This lets smoldot execute runtimes that verify bandersnatch ring-VRF proofs (proof-of-personhood chains). The remaining RFC-0163 functions (Pallas, Vesta) are registered but unimplemented. ([#3331](#3331); fixes [#3328](#3328)) ### Fixed - Fix a panic (`assertion failed: task.event_pending_send.is_none()` in debug builds) or a silently lost connection event (release builds, later causing a sync service panic on an unmatched `Disconnected`) when a peer ban raced with a network event that was still being delivered to subscribers. ([#3314](#3314); fixes [#3312](#3312)) - No longer crash with an uncaught `InvalidStateError` when sending on an `RTCDataChannel` that left the `open` state before its `close` event was delivered; the send is skipped, since the pending `close` event resets the stream anyway. ([#3324](#3324); fixes [#3322](#3322)) - In remote-instance mode, no longer crash with an uncaught `TypeError` when a message addressed to the first substream of a WebRTC connection (stream id 0) raced with that substream's reset: stream id 0 was accidentally exempt from the stale-message check. ([#3326](#3326); related to [#3322](#3322)) - No longer crash with an uncaught `InvalidStateError` when opening a substream on an `RTCPeerConnection` that moved to `closed` before its `connectionstatechange` event was delivered. ([#3327](#3327); fixes [#3325](#3325)) - Fix a panic in the connection task when the remote resets an inbound notifications substream while a message about that substream is still in flight (a duplicate reject, or a close right after an accept). ([#3329](#3329); fixes [#3304](#3304))
npm smoldot v3.4.0 (#3333) This is to: - publish `smoldot-v3.4.0` npm. - publish crates `smoldot-light v2.0.0`, `smoldot v2.2.0` ## Changes ### Added - Implement the [RFC-0163](https://github.com/polkadot-fellows/RFCs/blob/main/text/0163-ec-host-functions.md) elliptic curve host functions: scalar multiplication and multi-scalar multiplication on bandersnatch (`ed_on_bls12_381_bandersnatch`), and scalar multiplication, multi-scalar multiplication, multi Miller loop and final exponentiation on BLS12-381. This lets smoldot execute runtimes that verify bandersnatch ring-VRF proofs (proof-of-personhood chains). The remaining RFC-0163 functions (Pallas, Vesta) are registered but unimplemented. ([#3331](#3331); fixes [#3328](#3328)) ### Fixed - Fix a panic (`assertion failed: task.event_pending_send.is_none()` in debug builds) or a silently lost connection event (release builds, later causing a sync service panic on an unmatched `Disconnected`) when a peer ban raced with a network event that was still being delivered to subscribers. ([#3314](#3314); fixes [#3312](#3312)) - No longer crash with an uncaught `InvalidStateError` when sending on an `RTCDataChannel` that left the `open` state before its `close` event was delivered; the send is skipped, since the pending `close` event resets the stream anyway. ([#3324](#3324); fixes [#3322](#3322)) - In remote-instance mode, no longer crash with an uncaught `TypeError` when a message addressed to the first substream of a WebRTC connection (stream id 0) raced with that substream's reset: stream id 0 was accidentally exempt from the stale-message check. ([#3326](#3326); related to [#3322](#3322)) - No longer crash with an uncaught `InvalidStateError` when opening a substream on an `RTCPeerConnection` that moved to `closed` before its `connectionstatechange` event was delivered. ([#3327](#3327); fixes [#3325](#3325)) - Fix a panic in the connection task when the remote resets an inbound notifications substream while a message about that substream is still in flight (a duplicate reject, or a close right after an accept). ([#3329](#3329); fixes [#3304](#3304))
npm smoldot v3.4.0 (#3333) This is to: - publish `smoldot-v3.4.0` npm. - publish crates `smoldot-light v2.0.0`, `smoldot v2.2.0` ## Changes ### Added - Implement the [RFC-0163](https://github.com/polkadot-fellows/RFCs/blob/main/text/0163-ec-host-functions.md) elliptic curve host functions: scalar multiplication and multi-scalar multiplication on bandersnatch (`ed_on_bls12_381_bandersnatch`), and scalar multiplication, multi-scalar multiplication, multi Miller loop and final exponentiation on BLS12-381. This lets smoldot execute runtimes that verify bandersnatch ring-VRF proofs (proof-of-personhood chains). The remaining RFC-0163 functions (Pallas, Vesta) are registered but unimplemented. ([#3331](#3331); fixes [#3328](#3328)) ### Fixed - Fix a panic (`assertion failed: task.event_pending_send.is_none()` in debug builds) or a silently lost connection event (release builds, later causing a sync service panic on an unmatched `Disconnected`) when a peer ban raced with a network event that was still being delivered to subscribers. ([#3314](#3314); fixes [#3312](#3312)) - No longer crash with an uncaught `InvalidStateError` when sending on an `RTCDataChannel` that left the `open` state before its `close` event was delivered; the send is skipped, since the pending `close` event resets the stream anyway. ([#3324](#3324); fixes [#3322](#3322)) - In remote-instance mode, no longer crash with an uncaught `TypeError` when a message addressed to the first substream of a WebRTC connection (stream id 0) raced with that substream's reset: stream id 0 was accidentally exempt from the stale-message check. ([#3326](#3326); related to [#3322](#3322)) - No longer crash with an uncaught `InvalidStateError` when opening a substream on an `RTCPeerConnection` that moved to `closed` before its `connectionstatechange` event was delivered. ([#3327](#3327); fixes [#3325](#3325)) - Fix a panic in the connection task when the remote resets an inbound notifications substream while a message about that substream is still in flight (a duplicate reject, or a close right after an accept). ([#3329](#3329); fixes [#3304](#3304))
npm smoldot v3.3.2 (#3311) This is to: - publish `smoldot-v3.3.2` npm. - publish crates `smoldot-light v1.3.2`, `smoldot v2.1.1` ## Changes ### Changed - Match incoming statements against statement-store subscriptions through a topic index instead of scanning every subscription, making statement matching efficient when many subscriptions are active. Filter semantics are unchanged. ([#3281](#3281); fixes [#3144](#3144), [#3147](#3147)) ### Fixed - Fix a panic (`called Result::unwrap() on an Err value` in `runtime_service`) during parachain sync, caused by a relay chain block being unpinned twice when its parahead fetch finished but the block was pruned before being reported. ([#3287](#3287); fixes [#3286](#3286)) - No longer crash the entire client when WebRTC is unavailable in the environment (e.g. inside a worker thread, where `RTCPeerConnection` doesn't exist); WebRTC connections are now forbidden instead. ([#3303](#3303); fixes [#3302](#3302)) - JS exceptions thrown by code called from within the Wasm are no longer silently swallowed (which left an unusable instance and misleading errors on later calls); they now trigger the regular crash handling with a `wasm-panic` event carrying the original message and stack. ([#3308](#3308); related to [#3302](#3302), [#3306](#3306), [#3307](#3307)) - Fix a panic (`same stream_id used multiple times in connection_stream_opened`) when a browser delivers the `open` event of an `RTCDataChannel` more than once. ([#3309](#3309); fixes [#3305](#3305)) Also updates `docs/RELEASING.md` step 5: changelog entries now link related GitHub issues.
npm smoldot v3.3.2 (#3311) This is to: - publish `smoldot-v3.3.2` npm. - publish crates `smoldot-light v1.3.2`, `smoldot v2.1.1` ## Changes ### Changed - Match incoming statements against statement-store subscriptions through a topic index instead of scanning every subscription, making statement matching efficient when many subscriptions are active. Filter semantics are unchanged. ([#3281](#3281); fixes [#3144](#3144), [#3147](#3147)) ### Fixed - Fix a panic (`called Result::unwrap() on an Err value` in `runtime_service`) during parachain sync, caused by a relay chain block being unpinned twice when its parahead fetch finished but the block was pruned before being reported. ([#3287](#3287); fixes [#3286](#3286)) - No longer crash the entire client when WebRTC is unavailable in the environment (e.g. inside a worker thread, where `RTCPeerConnection` doesn't exist); WebRTC connections are now forbidden instead. ([#3303](#3303); fixes [#3302](#3302)) - JS exceptions thrown by code called from within the Wasm are no longer silently swallowed (which left an unusable instance and misleading errors on later calls); they now trigger the regular crash handling with a `wasm-panic` event carrying the original message and stack. ([#3308](#3308); related to [#3302](#3302), [#3306](#3306), [#3307](#3307)) - Fix a panic (`same stream_id used multiple times in connection_stream_opened`) when a browser delivers the `open` event of an `RTCDataChannel` more than once. ([#3309](#3309); fixes [#3305](#3305)) Also updates `docs/RELEASING.md` step 5: changelog entries now link related GitHub issues.
npm smoldot v3.3.2 (#3311) This is to: - publish `smoldot-v3.3.2` npm. - publish crates `smoldot-light v1.3.2`, `smoldot v2.1.1` ## Changes ### Changed - Match incoming statements against statement-store subscriptions through a topic index instead of scanning every subscription, making statement matching efficient when many subscriptions are active. Filter semantics are unchanged. ([#3281](#3281); fixes [#3144](#3144), [#3147](#3147)) ### Fixed - Fix a panic (`called Result::unwrap() on an Err value` in `runtime_service`) during parachain sync, caused by a relay chain block being unpinned twice when its parahead fetch finished but the block was pruned before being reported. ([#3287](#3287); fixes [#3286](#3286)) - No longer crash the entire client when WebRTC is unavailable in the environment (e.g. inside a worker thread, where `RTCPeerConnection` doesn't exist); WebRTC connections are now forbidden instead. ([#3303](#3303); fixes [#3302](#3302)) - JS exceptions thrown by code called from within the Wasm are no longer silently swallowed (which left an unusable instance and misleading errors on later calls); they now trigger the regular crash handling with a `wasm-panic` event carrying the original message and stack. ([#3308](#3308); related to [#3302](#3302), [#3306](#3306), [#3307](#3307)) - Fix a panic (`same stream_id used multiple times in connection_stream_opened`) when a browser delivers the `open` event of an `RTCDataChannel` more than once. ([#3309](#3309); fixes [#3305](#3305)) Also updates `docs/RELEASING.md` step 5: changelog entries now link related GitHub issues.
PreviousNext