Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

10/WAKU2: Define supported transports in spec #458

Closed
oskarth opened this issue Sep 7, 2021 · 1 comment
Closed

10/WAKU2: Define supported transports in spec #458

oskarth opened this issue Sep 7, 2021 · 1 comment

Comments

@oskarth
Copy link
Contributor

oskarth commented Sep 7, 2021 •
edited
Loading

Problem

Currently it isn't well-specified which transport MUST or MAY be specified. While any transports may be used with libp2p, by defining a minimum baseline this helps for interop between clients, such as between js-waku and nim-waku.

Acceptance criteria

Transports mentioned in main spec. Similar to: https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#transport

Specifically, support for Websockets elaborated on here.
@oskarth oskarth mentioned this issue Sep 7, 2021
Closed
5 tasks
@jimstir jimstir mentioned this issue Jun 13, 2024
Open
@jimstir
Copy link
Contributor

jimstir commented Jun 13, 2024

Issue is moved here

@jimstir jimstir closed this as completed Jun 13, 2024
@jimstir jimstir closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@oskarth @jimstir