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.
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.