Alex Potsides

I'm closing this issue because I think the underlying problem you mention in #2454 is that your observed addresses are not being confirmed by peers. Exposing libp2p internals like this...

When confirming an observed address, the AutoNAT protocol requires several confirmations from a diverse range of network peers. This is by design to make it harder to trick your node...

@danisharora099 yes, that's the right place for this issue. Unfortunately I don't think GitHub lets us transfer issues between orgs, only between repos in the same org so it'll have...

It might be enough to update the stream state in [YamuxStream.sendCloseWrite](https://github.com/ChainSafe/js-libp2p-yamux/blob/master/src/stream.ts#L145C9-L145C23) to be `StreamState.Finished`, then check `this.state` is not `StreamState.Finished` in [YamuxStream.sendWindowUpdate](https://github.com/ChainSafe/js-libp2p-yamux/blob/master/src/stream.ts#L271C3-L271C22) before sending the update. What do you think...

Oh, wow - that version of go-ipfs/kubo was released five years ago. I'm not sure it's still supported - is it not possible for you to upgrade?

Closing as this issue appears to have been resolved.

Thanks for opening this. This seems fair enough but I think exporting the class as a whole exposes too much of the internal API. For example it implements `Startable` -...

> I'm not sure how js-libp2p development is funded or organized. js-libp2p gets occasional grants from the libp2p foundation, though it's long-term state is fairly precarious. There's a [talk about...

This is by design to simplify the public API and allow internal refactors without breaking that public API. Typically internal components are only accessed by services, which are the way...

When implementing this I hadn't realised that libjuice will [only ever allow one UDP socket to be used](https://github.com/paullouisageneau/libjuice/issues/247) so unregistering the handler takes a host/port pair in order to unregister...