This is litterally the first time Delegation Pools have been attemtped to be explained to most of us so bear with us/me as we ask some questions.
Please feel free to ask anything, I made this post for that exact reason.
On the 40 account limit : the pool is not the end goal, I was confused by this too, basically :
may users can delegate to one pool, and each user can delegate to 40 pools max. The rc in the pool can then be used to be delegated to users, and then you can delegate to infinite accounts if you want.
Here's another example:
A,B,C delegate 30, 40, 60 rc to A's pool. A's pool contain 130 RC, but A can't use that rc to transact, A must delegate RC from that pool to users and then that RC will be usable.
Basically, the act of delegating RC doesn't happen when you contribute to a pool (40 per user), but when you delegate out of that pool (infinite).
Delegated RC out of a pool is not proportional, you can freely delegate 500 RC to one user and 3 to another. It's up to the pool owner to delegate whatever amount he sees fit.
OK putting RC into a pool may be complicated but really that's only a few people doing that. What we want to know is how to get the RC into the hands of users who do not have much RC>
We will see apps like ourselves and splinterlands putting a ton of RC into a pool for our users to use. Which will number into the thousands ... hopefully eventually tens of thousands (or more) users.
So i'm rereading what you wrote and it's not really clicking yet.
How does that part work. PeakD uses 100k SP worth of RCs. How does it go from there? Let's say there are 1000 users that need RC.
You delegate from the pool to each user let's say 100 hp worth of rc . And that's it assuming they have a slot set to steempeak.
In the coming days I'll post an example script, it'll make more sense for everyone if it's a more concrete example :)