In a first version, we can live with one known aggregator node per ORU chain. Later, we want at least a committee of nodes to be aggregators. In the latter case, the pubkeys still can be known upfront by clients (and they should).
Later, ideally, we want that every node can be an aggregator node. In that case the pubkeys can't be known upfront and this case requires more thinking.
We should also decide if we should implement this logic in the default execution environment (ref: #35) as opposed to (in golang) here or as an SDK module.
In a first version, we can live with one known aggregator node per ORU chain. Later, we want at least a committee of nodes to be aggregators. In the latter case, the pubkeys still can be known upfront by clients (and they should).
Later, ideally, we want that every node can be an aggregator node. In that case the pubkeys can't be known upfront and this case requires more thinking.
We should also decide if we should implement this logic in the default execution environment (ref: #35) as opposed to (in golang) here or as an SDK module.