Thomas Eizinger

> @thomaseizinger did you take a look at https://github.com/shadow/shadow? It compares itself to mininet, but claims to be more deterministic. I did not (yet). I've found mininet to be a...

> > I am in favor of exploring this early on. In my eyes Docker would significantly simplify build and package management. > > @thomaseizinger is there some way to...

> to see which protocols are requested. Perhaps there is a misunderstanding here but libp2p does not have a notion of _requesting_ protocols. Instead, nodes _offer_ certain protocols. This basically...

> I understand the identify stream is mandatory and the first requested stream This is definitely not the case and I'd advise caution in making it a requirement in your...

> > The rust-libp2p interop test binary will attempt to open a stream with the identify protocol to you. We had to add that because there is / was(?) a...

> > > to see which protocols are requested. > > > > Perhaps there is a misunderstanding here but libp2p does not have a notion of _requesting_ protocols. Instead,...

How does JS-libp2p solve this? I imagine it has the same issue.

> Sounds like a good idea. What that be copy of the ping test, or can we somehow add another dimension to the matrix? I think it should be as...

What is the progress on the V2 spec and the go implementation? I am interested in having V2 asap in `rust-libp2p` because with our recent release of kademlia client-mode, knowing...

> I'm busy finishing the smart dialing effort. [libp2p/go-libp2p#2394](https://github.com/libp2p/go-libp2p/issues/2394) is the last major piece left. I will pick AutoNAT v2 implementation after next week. I'll start addressing the open issues...