3 ms·

The real world problems are still being solved, just off-chain. I made a similar example with Mastodon: no central entity controls Mastodon, so x@x.com and x@x.

The real world problems are still being solved, just off-chain. I made a similar example with Mastodon: no central entity controls Mastodon, so x@x.com and x@x.xyz might be owned by different people, one impersonating another, and you can't just "complain to Mastodon" to fix it. Tornado cash: the domain is still resolvable to an IPFS hosted website[1]. As far as ENS is concerned as a name service and URI resolving mechanism, it is working great. This doesn't mean the smart contract that facilitates tornado cash deposits is working that well: if the US says you will be criminalized for touching a smart contract, then nobody will want to touch it, and tornado cash depends on many people using it to provide anonymity. > If you were actually concerned about censorship, an expensive service which leaves a public audit trail for prosecutors would not be the optimal starting point. If you are referring to tornado cash, I think you are mistaken. [1] https://twitter.com/liamzebedee/status/1578127982173908992 https://twitter.com/liamzebedee/status/1578127982173908992

acdha 4y ago
> The real world problems are still being solved, just off-chain. This is incorrect and the example shows why: > I made a similar example with Mastodon: no central entity controls Mastodon, so x@x.com and x@x.xyz might be owned by different people, one impersonating another, and you can't just "complain to Mastodon" to fix it. In this case, it might not be a problem — many people share the same names and a decentralized system supports that in a way which a centralized system like ENS does not. If it is a problem, you can complain to the operator of that particular instance and if it's an actual crime their domain registrar or hosting company, etc. If you lose your credentials or someone steals them, you can use the same mechanism to correct it. In the case of ENS, you not only do not have any of those mechanisms but the system is designed to prevent them. If you lose control of your keys, you lose your name for ever. If someone squats on your name, there's no third-party to turn to short of filing a lawsuit and hoping that the person complies with the eventual outcome. Re: Tornado cash, that's kind of the point – the smart contract is risky for people in multiple large economies to touch, and IPFS is no more resistant to take-down notices than any other distributed hosting option since it's built on top of the normal internet and governments have plenty of experience contacting network owners. Having the name up gives you something more reputable looking than using a DNS TLD under a different legal authority but it's not meaningfully making the system more available.
- web3isgoing 4y ago
  The fact that I can still access tornado cash website through IPFS and dAppnet does imply it is more accessible and censorship resistant. We are talking about ENS pointing to an IPFS website here, not the smart contract addresses that the ENS points to. In mastodon, if the impersonator is self hosting the impersonating domain, your only solution is to complain to the registrar or try to get support from other instances to block the domain. The same mechanisms of getting clients and servers to block requests happening in the censor resistant protocol does happen in ens and crypto based systems, if criminal behavior is involved or heavy moderation is wanted.

acdha 4y ago

> The real world problems are still being solved, just off-chain. This is incorrect and the example shows why: > I made a similar example with Mastodon: no central entity controls Mastodon, so x@x.com and x@x.xyz might be owned by different people, one impersonating another, and you can't just "complain to Mastodon" to fix it. In this case, it might not be a problem — many people share the same names and a decentralized system supports that in a way which a centralized system like ENS does not. If it is a problem, you can complain to the operator of that particular instance and if it's an actual crime their domain registrar or hosting company, etc. If you lose your credentials or someone steals them, you can use the same mechanism to correct it. In the case of ENS, you not only do not have any of those mechanisms but the system is designed to prevent them. If you lose control of your keys, you lose your name for ever. If someone squats on your name, there's no third-party to turn to short of filing a lawsuit and hoping that the person complies with the eventual outcome. Re: Tornado cash, that's kind of the point – the smart contract is risky for people in multiple large economies to touch, and IPFS is no more resistant to take-down notices than any other distributed hosting option since it's built on top of the normal internet and governments have plenty of experience contacting network owners. Having the name up gives you something more reputable looking than using a DNS TLD under a different legal authority but it's not meaningfully making the system more available.

web3isgoing 4y ago
The fact that I can still access tornado cash website through IPFS and dAppnet does imply it is more accessible and censorship resistant. We are talking about ENS pointing to an IPFS website here, not the smart contract addresses that the ENS points to. In mastodon, if the impersonator is self hosting the impersonating domain, your only solution is to complain to the registrar or try to get support from other instances to block the domain. The same mechanisms of getting clients and servers to block requests happening in the censor resistant protocol does happen in ens and crypto based systems, if criminal behavior is involved or heavy moderation is wanted.