search

unstoppabledomains / dot-crypto

Contracts and tools for .crypto
78 stars 38 forks source link

[REQ] Add support for IPNS for parity with ENS #42

Open brianddk opened 3 years ago

brianddk commented 3 years ago

ENS supports the context record type 0xe5 for IPNS records. This allows users to make changes on the IPFS layer without having to make changes at the block chain layer. This is preferable as it reduces the need for block chain transactions and fees.

And obvious choice would be dweb.ipns.hash

Reference:

aquiladev commented 3 years ago

there is no restriction for record's key in dot-crypto smart contracts. we have recommended list of keys, but you can set whatever you like, as well as dweb.ipns.hash

mvlabat commented 3 years ago

Hi @brianddk! Thanks for creating the issue.

We were considering adding support of IPNS records some time ago. The last time I was checking though, resolution performance was really poor. I believe it's something that the IPFS team is still working on to get it fixed (https://github.com/ipfs/go-ipfs/issues/3860). I wonder if your experience was different.

But it surely doesn't prevent us from adding it to the standard, which, of course, would be a better option than leaving our users to use a nonstandard key. We'll discuss it with the team. One of the things we'll also need to figure out is IPNS support in our browser extension.

cc @DeRain @bogdan @perfect-cents