Zeronet: Decentralized solution for .bit domain resolving

[up4]

If I have an up-to-date namecoin blockchain and with a local Namecoind service running, I would like ZeroNet to use its JSON RPC API instead of ZeroName for .bit domain name resolution.

If it has any chance of being pulled back for the next release I would like to submit a patch. Please let me know if there is interest.

[HelloZeroNet]

There is a plugin for that: https://github.com/HelloZeroNet/ZeroNet/tree/master/plugins/disabled-Zeroname-local

[up4]

OK, thanks. That's not what I meant and it was not functional when I tried it but I talked to the author ( @TheNain38 ) and he said he would fix it and try to implement the functionality I was referring to : that if a local instance of namecoind is running, to automatically switch to resolving .bit domains with it instead of relying on ZeroName. Can we leave this open until it is confirmed to work and turned on by default in a release or something ? Thanks.

[HelloZeroNet]

I prefer to make it an separate, optional plugin as it affects very small amount of users and it's not stable yet

[up4]

It's not stable, I agree. But, it does affect the overall perception that ZeroNet does not try very hard to be truly decentralized by forcing you to trust ZeroName, by _default_. Leaving this issue open shows that, well, it's a _known_ issue, at least.

[HelloZeroNet]

I think the best solution would be using P2P name resolution without downloading the blockchain. It could be possible using SPV clients, but it's not ready for namecoin yet: http://blog.namecoin.org/post/109811339625/lightweight-resolvers
when it's ready we will implement it as default dns resolving.

other possibility: https://blockstack.org/docs/light-clients (it's also not ready yet)

[up4]

i hear you and i agree but I think this should remain a ZeroNet open issue and recognized as such

[JeremyRand]

Hi @HelloZeroNet,

FYI the decentralized SPV client that @cassiniNMC talked to you about at GETD#4 is released in beta. The mode that Cassini discussed with you is leveldbtxcache.

The main reason it's classified as "beta" is that not many people have used it in production, so we just don't have a strong basis for knowing if there are any issues -- maybe that's where you can come in?

Cheers!