Right now we always subscribe to all data column sidecars which means no matter if you are supernode or not we receive and propagate all data columns.
|
if (ForkSeq[fork] >= ForkSeq.fulu) { |
|
// TODO: @matthewkeil check if this needs to be updated for custody groups |
|
for (let subnet = 0; subnet < DATA_COLUMN_SIDECAR_SUBNET_COUNT; subnet++) { |
|
topics.push({type: GossipType.data_column_sidecar, subnet}); |
It should probably work similar to attestation / sync committee subnets which are dynamic, ie. in case of data column subnets we need to adapt based on validator custody requirement.
There might be one edge case if we are proposer as we need to publish columns for all subnets.