• 0 Posts
  • 3 Comments
Joined 1 year ago
cake
Cake day: November 17th, 2023

help-circle

  • Competitive_Ebb_4124@alien.topBtoEthereumENS Question
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    We are having big trouble in the company I work at to pick a cool product name that isn’t already taken on the ENS. The previous name wasn’t registered in time and some random hoarder kidnapped it. Can’t say anything about actual stats for the whole ecosystem, but my personal experience points to most usage being hoarders, which kind of matches classical domain registrations.

    I don’t feel like any of those “investments” will really turn out tho, projects seem to prefer classic well known domains over ens ones.


  • There are some interop projects and thoughts about accessing cross rollup state and their basic idea would be to alleviate some of the pains, but one would still need account abstraction to be properly utilized to remove gas requirements. Furthermore dapps would need to integrate which is kind of a long shot. Overall it should get better, but perhaps not for everything and there will be some quirks as even with interop you won’t have direct state atomicity for cross layer 2 operations. Asset oriented dapps will have to work in isolation based on the specific network’s bridged assets. Unless they go another route which would introduce great latency to synchronize states, but this would break composability.

    So to answer your question - the UX might improve depending on your specific usage. Most of the current dApps will remain kinda clunky to use. And the ecosystem is definitely not going back to a single layer any time soon as there is no viable way to scale and optimize execution costs.