smol-dot/smoldot issues and pull requests

#122 - `smoldot-light-base` contains too much code

Issue - State: closed - Opened by tomaka about 2 years ago - 2 comments

#119 - GrandPa warp sync robustness to empty responses

Issue - State: closed - Opened by tomaka about 2 years ago

#117 - Implement Beefy

Issue - State: open - Opened by tomaka about 2 years ago - 4 comments
Labels: blocked

#112 - Smoldot should check the API version of the runtime specs before doing a call

Issue - State: open - Opened by tomaka about 2 years ago - 1 comment

#111 - Use only one network service for all chains

Issue - State: closed - Opened by tomaka about 2 years ago - 3 comments
Labels: priority-low

#111 - Use only one network service for all chains

Issue - State: closed - Opened by tomaka about 2 years ago - 3 comments
Labels: priority-low

#103 - Consider checking whether parachain has a slot at initialization

Issue - State: open - Opened by tomaka about 2 years ago - 1 comment

#99 - Periodically print debug info about chains with 0 peers

Issue - State: open - Opened by tomaka about 2 years ago - 2 comments

#97 - Implement generating a chain spec

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment
Labels: blocked

#93 - Full node should load consensus data from chain storage instead of storing it in database

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment
Labels: blocked

#91 - Consider using wasm threads in the wasm node

Issue - State: closed - Opened by tomaka about 2 years ago - 16 comments
Labels: blocked

#88 - Use wasm64 for the wasmnode when available

Issue - State: open - Opened by tomaka about 2 years ago - 1 comment
Labels: blocked

#88 - Use wasm64 for the wasmnode when available

Issue - State: open - Opened by tomaka about 2 years ago - 1 comment
Labels: blocked

#88 - Use `wasm64` for the wasm node when available

Issue - State: open - Opened by tomaka about 2 years ago - 1 comment
Labels: blocked

#85 - JSON-RPC: cap the total size of all the pending requests of each client

Issue - State: open - Opened by tomaka about 2 years ago - 1 comment

#84 - Panic in JSON-RPC service

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#83 - wasm-node: On panic, load a separate Wasm source map and resolve the backtrace

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment
Labels: blocked

#75 - Trusted light clients system

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#75 - Trusted light clients system

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#75 - Trusted light clients system

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#74 - Implementing answer block warp sync and storage requests from the light client

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#74 - Implementing answer block warp sync and storage requests from the light client

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#74 - Implementing answer block warp sync and storage requests from the light client

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#72 - Add unstable JSON-RPC function that exports recent networking events

Issue - State: open - Opened by tomaka about 2 years ago - 6 comments
Labels: priority-low

#70 - Internet connectivity and finality gap

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#68 - Fuzzing targets should be compiled with locked flag

Issue - State: closed - Opened by tomaka about 2 years ago
Labels: blocked

#68 - Fuzzing targets should be compiled with locked flag

Issue - State: closed - Opened by tomaka about 2 years ago
Labels: blocked

#68 - Fuzzing targets should be compiled with locked flag

Issue - State: closed - Opened by tomaka about 2 years ago
Labels: blocked

#68 - Fuzzing targets should be compiled with locked flag

Issue - State: closed - Opened by tomaka about 2 years ago
Labels: blocked

#67 - Properly handle warp syncing failures

Issue - State: closed - Opened by tomaka about 2 years ago

#66 - Deno documentation isn't great

Issue - State: open - Opened by tomaka about 2 years ago
Labels: priority-low

#61 - Panic in runtime_service

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#60 - Brainstorm and refactor the discovery process and address book

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#60 - Brainstorm and refactor the discovery process and address book

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#58 - In the new JSON-RPC API, reaching the limit to number of subscriptions shouldn't lead to a JSON-RPC error

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#53 - Panic related to peers cache

Issue - State: closed - Opened by tomaka about 2 years ago - 1 comment

#51 - Found WebRTC-related panic

Issue - State: closed - Opened by tomaka about 2 years ago - 2 comments
Labels: blocked

#47 - Refactor WebSocket handling by using a separate SingleStreamHandshakeKind

Issue - State: open - Opened by tomaka about 2 years ago - 1 comment
Labels: priority-low

#44 - The network key should periodically change

Issue - State: open - Opened by tomaka about 2 years ago - 4 comments
Labels: priority-low

#44 - The network key should periodically change

Issue - State: open - Opened by tomaka about 2 years ago - 6 comments
Labels: priority-low

#44 - The network key should periodically change

Issue - State: open - Opened by tomaka about 2 years ago - 6 comments
Labels: priority-low

#44 - The network key should periodically change

Issue - State: open - Opened by tomaka about 2 years ago - 4 comments
Labels: priority-low

GitHub / smol-dot/smoldot issues and pull requests