oskarth

https://status.im/build_status/status_go.html here or https://status.im/build_status/index.html

@kaiserd @easye What is the status of this?

While I agree we should do this, I think keeping it simple for now is the way to go. Once we have basic track(s) in place, it makes sense for...

Brief update: this is still not a priority, but something for further privacy enhancements once we have gotten Waku v2 shipped, I believe. cc @staheri14 for awareness as it relates...

@jm-clius if you feel differently about this feel free to activate it again, otherwise seems unlikely we'll get to in Feb

@staheri14 could consider doing this as part of refactor&upstream week, taking existing analysis and opening issue/PR to libp2p specs/forum

To deal with fixed length indexing problem in e.g. Go, perhaps padding to a fixed length and using that would work? I'm sure a lot of codebases using multihashes also...

@decanus A good follow up issue on this would be to ensure there's a good story for compatibility and upgrades. That issue would then be a blocker for this one....

Ping re compatibility discussion issue

Where's the content? I see nothing that relates to actual consensus mechanism. It shouldn't take that long to get basic semantics done considering a lot has been written already