If the network had no computational bounds and was run on nuclear energy sure, but a lot of the nodes are people struggling to keep up with the current, ever increasing minimum requirements, and a lot of that energy is spinning turbines with steam from burning stuff. I don't understand why the contracts can't be iterated through... The network parameters are always known. If you can move them out in piecemeal then while it's a bug, it's not a blackhole.

Can I see what yu were reading?

Yes, there's a talented group that builds tools for the community. Many actually. They range from sites (graph explorers, big data, etc), to various niches like Pool Operator tools. They are well rewarded for the hours on ongoing OSS work. As an example, one tool was communally improved into a pretty polished piece of SPO software, it can tell you your block slots, if any, in the current, previous and next epoch. This isn't magic, IOHK goes out of its way to use English with equations. But forgive me if I failed, I cannot find the discussion about private centralized Slot Leader databases.

I got my numbers from Activity Monitor which I only quote when I need a program that approaches metrics with a white-hot spotlight, exacerbating their performance flaws. But I confirmed it in htop There really is a thread pegged at full load, while three or four other threads dance between not much and 60%. Watch it in non-threaded mode and the CPU time used for the Wallet moves faster than a normal clock. I can't afford to flight the beta anymore.