Moving from ETH Mainnet to PoW

We would like to propose that the ENS fork and migrate back to the PoW chain. The merge has broken a lot of tools, and made it much more difficult to remain decentralized. Not so much because of the issues in PoS governance, but because it is extremely difficult now to deploy a full node of Ethereum technically. It is almost completely broken and barely held together.

Since the ENS is a DAO meant to serve every decentralized chain, we hereby float the idea of migration to a more suitable chain for the project. We strongly believe that the merge is not a success, and the problems with it are not addressed, nor will be addressed in the future.

Perhaps the ENS should become its own chain altogether!

2 Likes

Not going to happen.

7 Likes

After more frustration, we discovered the fine folks over at Lodestar are working hard to bring us unified nodes. However, their time reference is months, if not years. It is very weird nobody in the Ethereum community is talking about the difficulties, and centralization introduced by people like us going offline. Our node is still down because there are no adequate guides on what to do, and even if there were, it wouldn’t solve the bugs.

This does have a devastating near term impact on Ethereum development. A lot of what we have done now with ENS is broken, and we are probably just going to give up because it’s not been solved even with 3 devs, all doing smart contracts since 2016, have been trying to solve.

Using Infura or Alchemy is not an option. They don’t offer what we need, and that centralizes traffic.

As an individual, the merge makes my life too stressful. I’ve haven’t got anything done since the merge. Can’t say enough bad things from the technical side. I know many are wondering what the malaise is from in the ENS markets/registration, and no doubt this is a huge part.

The real takeaway from the merge is: Things were working, now they don’t.

Can you describe the factors that makes you describe the merge as a “failure”?

1 Like
  1. The merge was a breaking change to all full nodes, like ours used for data to run our backends.

  2. There is limited documentation for end users to run the Beacon client in parallel. We still haven’t got it to work to this day, and have basically given up. We are talking about three senior level engineers who have developed and run multi-million dollar backends currently in production.

Not just unable to fix for our needs, but totally broken, not running at all. Even if it did, it still wouldn’t be efficient. It’s a total unmitigated disaster.

  1. There is no work on documentation since this post was made. It’s a dead project basically. Nick came here to laugh at the idea without probably understanding the long term problem that will pretty much kill Ethereum as a whole.

Does ENS need Ethereum? It doesn’t. It can be migrated to any chain if the DAO wants.

All PoS solutions are all suboptimal strategies if you care about decentralization, but it’s not about that. It’s simply not working on the technical side. Ethereum has the ENS and that’s it. There’s not one single project other than ENS worth using Ethereum for these days. It has no advantages over competitors except network (i.e. TLV), but we saw how fast people could move to Solana and other EVM chains like Polygon.

The ENS should really be prepared to move chains, because as it stands now Ethereum will fail.

NO! :face_with_spiral_eyes:

Are you aware of anyone else - outside your team - encountering the same problem that you have identified?
Not looking for names, more of a concensus view.

Might this be a case of general dissonance occuring within the Ethereum chain i.e. ‘we know it’s there, but if we don’t look at it directly, it might clear itself up before we have to address it’?

DEVCON had several tutorials about how to set up and run nodes on the PoS network.

I haven’t watched all, but here are some examples:

Do any of those help?

2 Likes

I just happened to be passing, saw the thread and thought I would comment.

From what I know. ENS (ie fredbloggs.eth style names) was one of the few successes in the Ethereum system. It is a good idea and it seems fairly well supported here and in 3rd party dapps. Is this thread implying it has been broken since the merge and the only way to fix it is by pretending the merge never happened? I would have thought by now Ethereum PoW was dead and not really worth going back to. I could see that the concept would work on any blockchain (if it hasn’t been implemented already) and that is an option. Still, i would have thought trying to find a fix for it was a fairly important thing to do.

If you did ditch ethereum, what would that do to all the .eths out there?

The merge broke backends that now have to run two buggy clients from different repos at once. There’s no solution to a few of the bugs so far, and you need to expend considerable time to mitigate them.

Another solution would be to move ENS to Polygon. While Polygon has a quite terrible dev experience for gaming too, they have improved a lot of services, and the ENS really wouldn’t be affected by the shortcomings.

Our project (after about $300k in development) decided top cease operations on ENS fwiw, in part because of this issue. Maybe things will be ok, but we voiced a valid opinion and got laughed at basically. The nodes aren’t coming back for now. Hopefully there can be something simple and unified in the future, but for now it’s a mess.

@unblockreceipts.eth
These are all staking related, so if you are interested in the ponzinomics of PoS, you can get a validator to run quite easily. While it is appreciated always a consolidation of links to tutorials, none of these are useful, and it is clear you don’t understand the problem here fully. Nodes are used as a point of truth for the entire history of Ethereum, not just before the merge, and not just after it. Projects need their own point of truth, and a way to avoid centralized bottlenecks like Infura or Alchemy, which also have their own issues post merge.

Are you aware of anyone else - outside your team - encountering the same problem that you have identified?
Not looking for names, more of a concensus view.

Yes, everyone has the same problem. It depends on the queries and project though. You can work around some of them, mostly by using centralized nodes.

Even the core developers don’t understand how big of a risk a poorly implemented solution like TheGraph is when it comes to decentralized queries as well. We discovered a major bug affecting a heavily relied on query there, and nobody is the wiser so far except the devs.

The best solution for many things is to just have a full or archival node, something now not really possible without a ton of pain. You will not figure this out at all if you are just coming to Ethereum.

Might this be a case of general dissonance occuring within the Ethereum chain i.e. ‘we know it’s there, but if we don’t look at it directly, it might clear itself up before we have to address it’?

Pretty much the political mindset of the Ethereum user which believes in DAOs and governance as a opposed to code is always law. It’s not a good or a bad philosophy, it is one of many ideologies, but in this case it is far to easy to pass the buck. The devs of the Beacon clients are most certainly aware and working towards a fix, but a lot of this problem is just rushing something unsupported out. Microsoft did this to everyone many times during the 90s and naughties for example. People have been conditioned to things being unilaterally broken for the sake of progress.

I know you have a bee in your bonnet about this, but this is not most peoples’ experience. Running clients post-merge is not substantially harder than running them pre-merge, and thousands of people and organisations are doing so. I myself am running a dappnode, which was as simple as setting it up and pressing ‘go’.

ENS is not migrating off Ethereum for the forseeable future, much less to a moribund PoW fork.

3 Likes