vyzo

It might also be not such a big deal in that the latency will be tree-optimized based on mesh transmission of messages. The `IHAVE`s will help correct overlay deficiencies and...

The stream is properly clsoed or reset in all branches. There is a test here: https://github.com/libp2p/go-libp2p-pubsub/blob/49274b0e8aecdf6cad59d768e5702ff00aa48488/comm.go#L38 If it is `EOF` then we can `Close` write and be done, in the...

We are working on adding a peer scoring function to gossipsub, such that peers can be assigned some score when the mesh is full and need to prune. Re: validation:...

Note that the peer scoring function can also be utilized when first constructing the mesh so that we build a good mesh to begin with.

The mesh should adapt organically to score changes: as peers come and go the mesh expands and contracts. The scoring will come into play when decisions to graft or prune...

Actually, regarding the score delay, you might simply want to delay joining your topics until you have finished the handshake and established a score.

@mcdee take a look at the peer score integration in #263. It allows for an application level score, which if negative will remove the peers from the mesh and only...

take a look at the spec in https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md 1. If the score of a peer drops below the `graylistThreshold`, then it will be totally ignored. 2. It is computed live...

I am a little confused by this. If a validator rejects a message, then it will not be published further.

Yes, but they still have to validate the message to accept it. There is no mechanism to limit the peers that receive the message, other than using a different topic.