Author: Kaz Wesley 2014-08-01 01:00:06
Published on: 2014-08-01T01:00:06+00:00
In an email exchange between Gregory Maxwell and Kaz Wesley, they discussed the possibility of developing a rule for what to keep in order to avoid false negatives or a huge storage requirement. The prototype Kaz is working on will provide data on the false-positive-missing-tx rate with something like "remember-last-N". There are various ways this rule could be upgraded to nearly eliminate the false-positive-missing rate, including learning what txes a peer has dropped via periodic mempool syncing or specifying the rule explicitly with priority scripts. All of these changes synergize, but as long as the simplistic remembering rule yields worthwhile improvement over the current approach, they can all be done independently as incremental improvements. The idea of mempool synchronization brings up the issue of transaction expiration since lack of mempool syncing is currently the mechanism for tx expiry. They also discussed the benefits of channel memory sparseblocks and FEC-based mempool synchronization. Gregory believes that minimizing latency in the face of multiple peers is the only reason to implement FEC at block forwarding time that can't be realized by FEC-based mempool synchronization, implemented separately from channel-memory based index-coding.
Updated on: 2023-06-09T01:08:16.055980+00:00