oskarth
oskarth
> Send Epoch and Send Count MUST be increased every time a record is retransmitted. Although no function is defined on how to increase Send Epoch, it SHOULD be exponentially...
# Problem Currently 14 is pointing to previous spec. It should point to the new one. See https://github.com/vacp2p/rfc/issues/412 for more details
This is a list of possible weaknesses, unknowns and enhancements of https://github.com/vacp2p/rfc/pull/413 The goal is to collect requirements and identify potential issues in the existing behavior. ## List of things...
As we are working on PubSub we are likely to find issues that we want to upstream. Here's a list of such issues, as reminders: Issues: - [ ] libp2p/specs...
These are things that can be improved in the current remote log design. No specific order. More details on each should be turned into its own issue, unless small enough...
## Problem Status as a consumer of SOB (see https://github.com/status-im/ideas/issues/10) wants to use it as much as possible. To do this there is a high-priority problem that we need to...
We want to make sure the mixnet layer and above data sync layers interface properly, and that we are mindful of any friction that might result. See https://discuss.status.im/t/data-sync-next-steps-and-considerations/1056 for next...
Size of packet: minimum and maximium size (4K) How fast are they sent? How often want to send message? How many clients? Not single group. Over mixnet. Typical usage.
Main issue will be upstream in libp2p, but this captures issue from this end. https://github.com/libp2p/libp2p/issues/71
Understand what attack vectors are possible here, study prior art and write up trade-offs / justification for given choice. Some raw notes: - One approach is to use a Friend-to-Friend...