I didn't understand what you mean by "operating an rc pool"
Someone is in charge of deciding what proportion of the RC in a pool goes to each user of the pool right? One user of the pool can't come in and use up all RC there are limits set and thus someone is setting it that makes them the operator. Right?

So what do these transactions look like? It's a new system right not like a json transaction but something specifically designed for this and existing in HiveD?

More or less I'm hoping my example on this post maybe helps someone in testing. Imagine we have a million active users later this year because we are working with 10 different youtuber friends and helping them create communities. Most of those users are their fans so a bunch are mostly silent readers who come in and check the communities and maybe do a little community chatting. If they use RC power it's likely from marking their notifications as read and posting a couple comments on community posts they find interesting and doing a bunch of votes (which don't have much HP attached to them)

There are of course still tens of thousands of that million who post actual content-posts and use significantly more RC power. Also side note: what happens at 1 million users does rc costs per transaction get much more expensive in the RC system? Or less?

So I assume at 1 million users our pool wouldn't need to be 10million HP worth of RC credits because they're not all coming in on the same day and doing the same amount and like i said many of them are just making comments and hitting the vote button a few times.

Seems like seeing what's going on with a pool will be important to those delegating to a pool so they can see in realtime what pools may need more attention.