You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IPNS is not a great solution for dynamic content on .eth domains. It is an eventually consistent model, which suffers from all the same problems as DNS - stale caches. We live in 2022, and can design a better system. It's interesting because you can see people looking for the alternative - ie. DNSLink. DNSLink is where you put the IPNS key pointing to the new content, inside the DNS system, thus defeating the whole decentralization property. had a good chat with noah from uniswap about this.
Here's an idea:
an uncensorable domain (.eth)
with uncensorable content attached to it (ipfs/bittorrent)
that can be updated cheaply ($0.01c) - on an L2.
that is more reliable than IPNS - in that the domain content is consistently, rather than eventually consistent (up to 24h on the IPFS DHT to update an IPNS domain properly)
that is privately and anonymously owned - only data you can see is what the domain points to.
We can build this using ZK tools today. Here's a small proposal:
deploy a fork of ENS on an L2 like Optimism/Arbitrum
write a ZK circuit in Circom that allows people to anonymously buy domains.
write a ZK circuit in Circom that allows people to anonymously update domain content (contenthash).
see what happens
The text was updated successfully, but these errors were encountered:
IPNS is not a great solution for dynamic content on .eth domains. It is an eventually consistent model, which suffers from all the same problems as DNS - stale caches. We live in 2022, and can design a better system. It's interesting because you can see people looking for the alternative - ie. DNSLink. DNSLink is where you put the IPNS key pointing to the new content, inside the DNS system, thus defeating the whole decentralization property. had a good chat with noah from uniswap about this.
Here's an idea:
We can build this using ZK tools today. Here's a small proposal:
The text was updated successfully, but these errors were encountered: