raffy

tbh, i'm always impressed by no-coiner and armchair bitcoiner comments -- it's like listening to a straight-edge discuss psychedelics -- how can you comment on a space you *clearly* don't understand?

Comment · 3 years ago

>SEC has already provided clarity on crypto

oof, so...is Ether a security?

Is this tweet an exchange? https://twitter.com/hoffmang/status/1515797969802436608

Comment · 3 years ago

ENS has DNS import via TXT Record verification proof, so the entire DNS tree can coexist in ENS trustlessly as long as future ENS-only TLDs are chosen wisely (seems simple: just use 0x80+ Unicode.) For example, try resolving my domain, "raffy.antistupid.com" in ENS.

I believe, the ENS registry only contains "eth" as an rogue node (also "[0-9a-f]{40}.addr.reverse" is used for wallet names). Recently, ".art" started offering tokenized names, where you get both DNS and ENS.

Comment · 3 years ago

> I hope this idea catches on

This already exists with Ethereum Name Service (ENS) https://ens.domains and Sign-in With Ethereum.

Comment · 3 years ago

I have tool which lets you scroll through all characters in a large document. It also shows names, scripts, and IDNA-like status.

https://adraffy.github.io/ens-normalize.js/test/chars.html

Comment · 3 years ago

I've created a bunch of Unicode tools for Ethereum Name Service (ENS).

https://adraffy.github.io/ens-normalize.js/test/resolver.htm...

Also:

https://adraffy.github.io/ens-normalize.js/test/emoji.html

https://adraffy.github.io/ens-normalize.js/test/chars.html

https://adraffy.github.io/ens-normalize.js/test/confused.htm...

https://adraffy.github.io/punycode.js/test/demo.html

Here is a video of another failure case:

https://twitter.com/adraffy/status/1629262969581473792

Comment · 3 years ago

FYI, there is a new ENS normalization spec on the horizon: https://github.com/adraffy/ens-normalize.js

https://adraffy.github.io/ens-normalize.js/test/resolver.htm...

Comment · 4 years ago

>and also a reasonably good explanation of why, at least in my opinion, crypto is still completely non-viable as a real medium of exchange

I understand HN is a shit-on-crypto echo chamber but it's naive to think crypto is just settlement.

Settlement is simply a low-level primitive. With smart contracts, you can build whatever mechanism you want before making something final. Multisig, clawbacks, timed-delays, time-locks, escrow, recovery wallets, etc.

Comment · 4 years ago

For a .eth name, this is trivial: provide operator approval to N-additional wallets

Comment · 4 years ago

Unfortunately, this is only single-character confusables. There are an enormous number of permutations missing (ѐ [450] vs è [E8]). The confusable matching isn't even reflexive (A confuse B, but B doesn't confuse A).

I've been developing a normalization library for Ethereum Name Service: https://adraffy.github.io/ens-normalize.js/test/resolver.htm...

Comment · 4 years ago

I'm trying to find the best combination of UTS-46, UTS-51, UTS-39, and prior work on IDN resolution w/r/t confusables: https://adraffy.github.io/ens-normalize.js/test/report-confu...

Personally, I found the Unicode spec very messy. Critical information is all over the place. You can see the direct effect of this when you compare various packages across different languages and discover that every library disagrees in multiple places. Even JS String.normalize() isn't consistent in the latest version of most browsers: https://adraffy.github.io/ens-normalize.js/test/report-nf.ht... (fails in Chrome, Safari)

The major difference between ENS and DNS is emoji are front and center. ENS resolves by computing a hash of a name in a canonicalized form. Since resolution must happen decentralized, simply punting to punycode and relying custom logic for Unicode-handling isn't possible. On-chain records are 1:1, so there's no fuzzy matching either. Additionally, ENS is actively registering names, so any improvement to the system must preserve as many names as possible.

At the moment, I'm attempting to improve upon the confusables in the Common/Greek/Latin/Cyrillic scripts, and will combine these new grouping with the mixed-script limitations similar to IDN handling in Chromium.

Interactive Demo: https://adraffy.github.io/ens-normalize.js/test/resolver.htm...

Also this emoji report is pretty cool: https://adraffy.github.io/ens-normalize.js/test/report-emoji...

Comment · 4 years ago

> But this is actually good, nuanced stuff.

What's good about it? Half the post is about Bitcoin. A large chunk is about the ENS token distribution.

There's no link to any of the contracts or code. There's no comparison with existing providers and the trade-offs. There's no discussion on how DAOs are still very immature and evolving. There's no acknowledgement of how ENS has behaved since inception.

Flash loan voting? Clueless.