smoldot

This is to:

• publish smoldot-v3.6.0 npm.
• publish crates smoldot-light v2.1.0, smoldot v4.0.0

Changes

Added

• sudo_unstable_metrics JSON-RPC function returning a snapshot of
  internal counters and gauges (connections, per-protocol request outcomes
  and durations, peer bans, gossip peers, verified blocks and finality
  proofs, block heights, warp-sync progress, runtime compilations, dropped
  transactions). Metric list and labels are unstable. (#3318; fixes #3285)
• lifecycle_unstable_follow / lifecycle_unstable_unfollow JSON-RPC
  functions reporting the chain's lifecycle state (connecting, syncing,
  ready, peer count, stall detection). (#3353; fixes #3301)

Fixed

• statement_subscribeStatement sends an empty first newStatements
  batch and drops expired or proof-less gossiped statements, like a full
  node. (#3371; related to #3349)
• GRANDPA justifications are now checked for pre-commit vote ancestry
  through votes_ancestries, not only signatures and threshold. (#3355)
• No longer panic in the legacy JSON-RPC API when a block is pruned
  before it was announced; such blocks also no longer leak into
  chainHead_v1_follow prunedBlockHashes. (#3366; fixes #3367)
• chainHead_v1_follow no longer loses a pinned-blocks budget slot for
  every block unpinned early. (#3366)
• On NodeJS, TCP connection failures and remote closes are reported
  immediately with the socket error as reason, instead of after the 4
  second handshake timeout. (#3364)
• statement_submit answers 7001 for the removed Proof::OnChain proof
  instead of broadcasting it. (#3370; related to #3349)

This is to:

• publish smoldot-v3.5.0 npm.
• publish crates smoldot-light v2.0.2, smoldot v3.0.0

Changes

Changed

• statement_submit validates statements like a full node (expiry,
  size, proof) and answers invalid with alreadyExpired,
  encodingTooLarge or noProof. Undecodable payloads and statements no
  peer accepted are now JSON-RPC error 7001.
  (#3344; fixes
  #3349)

Fixed

• chain_getBlock returns justifications as a sibling of block,
  matching SignedBlock, so Substrate clients can decode the response.
  (#3363; related to
  #3288)
• Recover WebRTC connections after a peer restart: substream opens time
  out after 20 s and the connection is reset and re-dialed.
  (#3361)
• Fix a connection task panic when a substream close or notification
  crosses a remote reset.
  (#3361)
• No longer ban peers for justifications that target a block too far
  ahead. (#3361)
• Bump arkworks to 0.6; a malformed elliptic curve host function input
  no longer aborts the process.
  (#3356)

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
  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; fixes
  #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;
  fixes #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; fixes
  #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; related to
  #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; fixes
  #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; fixes
  #3304)

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; fixes
  #3144,
  #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; fixes
  #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; fixes
  #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; related to
  #3302,
  #3306,
  #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; fixes
  #3305)

Also updates docs/RELEASING.md step 5: changelog entries now link
related GitHub issues.

Remove

• Removed MalformedJsonRpcError. Malformed JSON-RPC requests now later generate an error JSON-RPC response where the id field is equal to null, in accordance with the JSON-RPC 2.0 specification. (#1116)

Changed

• Transactions submitted through the JSON-RPC server before the warp syncing process is finished will now immediately be dropped. (#1110)
• JSON-RPC requests that are very large are no longer rejected. In case where the JSON-RPC client is trusted, then there is nothing to do, and the potential lack of memory space will become a non-issue once the Memory64 WebAssembly proposal becomes widely available. In case where the JSON-RPC client is not trusted, the API user is encouraged to manually implement a limit to the size of JSON-RPC requests, as it should do already right now anyway. (#1115)

Fixed

• Fix Chain.remove() not actually removing the chain until the warp syncing process is finished (which might never happen if for example bootnodes are misconfigured). (#1110)
• Fix JSON-RPC server not processing requests if many transactions are submitted before the warp syncing process is finished. (#1110)

Fixed

• Fix Deno throwing an exception when failing to connect to an unreachable node through a TCP/IP multiaddr. (#246)

Removed

• Removed Chain.databaseContent function. Use the chainHead_unstable_finalizedDatabase JSON-RPC function to obtain the database content instead. (#2791)

Changed

• Chain.sendJsonRpc now throws a MalformedJsonRpcError exception if the JSON-RPC request is too large or malformed, or a QueueFullError if the queue of JSON-RPC requests of the chain is full. (#2778)
• Removed AddChainOptions.jsonRpcCallback. Use the new Chain.nextJsonRpcResponse asynchronous function to pull JSON-RPC responses instead of registering a callback. A AddChainOptions.disableJsonRpc flag is now supported in order to bring the same effects as not passing any jsonRpcCallback. (#2778)
• Removed the version field of the struct returned by the rpc_methods function. (#2756)

Fixed

• Fix several panics related to cancelling the opening of incoming substreams. (#2785)
• Fix old runtimes not being cleaned up properly and runtimes being downloaded multiple times after an on-chain runtime upgrade. (#2781)