Serenity Validators, As Official Decentralized Casper Staking Pool Smart Contracts

[taoteh1221]

I'm a total novice at cryptocurrency tech, but was thinking it might be feasible to have each Serenity validator instead of being X number of randomly chosen accounts that meet certain criteria, be X number official Casper decentralized staking pool smart contracts instead? Wouldn't this simultaneously solve these two potential issues:

1. Everybody can participate in staking at any time, with any amount of ETH.

2. With multiple official decentralized staking pools to choose from that are all identical protocols, pool centralization issues cannot easily occur.

Sorry if I'm missing something here from a technical perspective, I'm just a web2 guy for now (slowly getting there with web3).

[Smithgift]

Here's a technical bugaboo: CASPER validators must have static validating code so that bets are verifiable on an absolute level. Because of this, a pool's multisig (assuming that's the most likely way to work these things) must remain constant from the moment of its creation. Because of that, there's no way for members to easily enter or leave, without completely rebuilding the pool.

[taoteh1221]

Maybe there is a workaround for this, via loading up a staking pool smart contract with participants before it goes live, then locking it down so it's ready to enter a validator cycle. Then have the existing live pools expire / release deposits and earnings after a certain period of time, and the new ready and waiting pool takes it's place...having no more than 1 pool fully loaded up and locked in waiting to go live, and 1 additional pool actively still loading up with participants (and locking in when the other pool goes live as a validator).

[github-actions]

There has been no activity on this issue for two months. It will be closed in a week if no further activity occurs. If you would like to move this EIP forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.

[github-actions]

This issue was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment.