Multiple Heads per hydra-node

[ch1bo]

trafficstars

Why

To optimize resource usage, users might want to have a single hydra-node be able to maintain and interact with multiple Hydra heads. If the peer nodes of multiple hydra heads are overlapping, the network connections could be re-used. Also, there might be use cases where within the same group of actors, a head shall be already opened why another head is still in it's finalization phase.

What

We would need to make the business logic in the hydra-node aware of multiple HeadStates, keep track of multiple heads on the chain layer and also scope the API accordingly to allow clients specify which head they want to query/interact with.

TBD

This is still very vague in motivation and what needs to be touched to make this happen. Gut feeling right now: it's involved.