vyzo

Duplicate consumption can be implemented by the application through a custom tracer, just like the score subsystem plugs into the tracer. The validator cache, which is complex, is then unecessary.

Maybe we can simply reference count the closures?

travis fails with: ``` ./gossipsub.go:361:6: no new variables on left side of := ```

It would be quite unwieldy to provide feedback on this from the library. When is the message considered sent? When it has entered the main loop? When it has been...

That sounds like backpressure from the network stack, is the receiver live?

Care to elaborate for future reference?

ok, thanks.

I think it will be a great feature to decouple subscription from routing, especially with gossipsub. We can use it to offer pubsub services in the core network, without spawning...

Nothing special is needed -- the routers already implement the `Relay` operation, while the subscription is handled by the core of pubsub. This is pretty simple to do, nothing needs...

Subscribers should be relays, we don't want leeches.