We are using the w3name service for making sure our IPNS keys are constantly republishing. w3name announced they would be deprecating the service in January.
Does anyone know about any good alternatives? Or is this the writing on the wall that we should build this service out in-house?
Here’s a blog post that outlines how we are using IPNS: https://blog.dappling.network/adding-ens-support-to-dappling/
For other readers, if you follow the link they do say why they didn’t do this in-house from the beginning, basically crummy documentation about how to actually do it.
For the poster, I’d say that yes, if you have the resources to do it, this sounds like something you should do in-house. Maybe use Kubo for NS even if you use Helios for everything else? Kubo might be more mature and easier to set up for something like this.
Also, the main alternative to IPNS is DNSLink, and I don’t see that mentioned in your blog post. Maybe DNSLink would work for your case, and it sounds like you’d have the centralized platform to operate the nameserver needed for it, in-house.