oskarth
oskarth
# Problem Currently in spec it says: > Waku is a privacy-preserving peer-to-peer messaging protocol for resource restricted devices. as well as: > Resource restricted.These applications often run in constrained...
# Problem To the extent that we have "node identity", i.e. in the form of keypairs etc, this should be separate from PeerID. PeerID MAY be rotated, and tying it...
# Problem Some applications have a requirement for lower-latency direct communication as a group. This can be due to (soft) real time comm requirement. For example, video chat. This can...
# Problem There have been cases where people, including protocol devs, take "resource restricted devices/environments" to mean that Waku *only* focuses on this. And that, therefore, there's a need for...
# Original problem Sometimes the application might produce messages that don't need to be stored, an example would be a ping to show that you are online, or for example...
# 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...
# Problem As we are getting more and more projects using Waku v2, there's a need for specs to be stabilized so they can be relied upon to be stable...
### Discussed in https://github.com/vacp2p/rfc/discussions/397 Originally posted by **bgits** June 11, 2021 Having reliable timestamps would be valuable for a wide range of applications. Even accuracy within a range of minutes...
### Discussed in https://github.com/vacp2p/rfc/discussions/374 Originally posted by **oskarth** April 21, 2021 # Problem Just knowing a peer is using STORE doesn't tell you much about what they are storing, if...
Subprotocol for packet reliability