Use W3name web sockets for updates

[juliangruber]

https://github.com/storacha/w3name/tree/main/packages/api#get-namekeywatch---receive-updates-via-websocket-when-new-values-are-published-to-a-name

Instead of polling Name.resolve() twice every 10 minutes every instance, only read it on process start (or test if the WebSocked emits the current value on connect), and then use the WebSocket API for updates.

This should both be faster for Station and cheaper for W3Name

Caveat: This might create too many open connections on W3Name, so test carefully.

[bajtos]

It makes me wonder - since IPNS was designed for peer-to-peer world, should we look into ways how to share the latest IPNS->IPFS CID mapping via p2p mechanisms like libp2p gossipsub? (Using w3name as a fallback or a way to boostrap the p2p state.)

[juliangruber]

The request load is currently not a problem for w3name, so this would be low priority. I agree that a more p2p solution would be better

[Winter-Soren]

Hey @juliangruber and @bajtos, Shall I work on this issue, if it hasn't been resolved?

[bajtos]

Hey @juliangruber and @bajtos, Shall I work on this issue, if it hasn't been resolved?

Sure, go ahead!