Considering that Eth2 also have about 7 clients that work today (with more being worked on), the specification is clearly understandable by at least 7 different entities, further eroding the argument that Eth2 specification is so complicated no one actually understands it.

Most of the linked spec is pseudocode - actually it looks like valid python code. So to be fair I highly doubt you'd need any understanding of what it's actually doing to successfully implement that spec. Just like I still have no clue how Quaternions work, yet I've implemented them multiple times.

How much would one need to pay you to test your hypothesis?

That is you try to implement a standard complaint new Eth2 implementation from scratch ( and possible record yourself while doing so.

That's just a random function description. The main thing here is how is seed calculated and analysis of whether it seed is safe from network partition, DDoS, malicious attack, nodes being offline, forks etc.

Also clearly documented and open to researchers to examine. The full code for the various Eth2 clients is open source.

[1] https://eth2book.info/altair/part2/building_blocks/randomnes...

[2] https://eth2.incessant.ink/book/06__building-blocks/02__rand...