Paul Harris
Paul Harris
> ```yaml > BLOB_SIDECAR_SUBNET_COUNT_PECTRA: 8 > # MAX_REQUEST_BLOCKS_DENEB * MAX_BLOBS_PER_BLOCK_PECTRA > MAX_REQUEST_BLOB_SIDECARS_PECTRA: 1024 > MAX_BLOBS_PER_BLOCK_PECTRA: 8 > TARGET_BLOBS_PER_BLOCK_PECTRA: 4 > ``` `PECTRA` would be `ELECTRA` here i assume...
i think most importantly the idea with that issue that's going to be implemented is not actually changing the produceBlock endpoint so we should make sure we check comments etc....
I think we can keep to spec unless we find actual reasons, will close.
Hey - thanks for raising this, we'll have a look at what's going on.
i think if we're wanting to go this way we want to put version on every type... One option would be to just add `versioned_attestation` to event stream v1... It...
> If we do that, does the `attestation` topic just handle phase0 attestations then? yes i would expect that it would just handle phase0, and you'd need a new topic...
quick update - currently its looking like we may be able to avoid this change, I've raised a question in discord.
closing as not planned at the moment.
It looks like some kind of warmup phase, if i remove the `fuzzVerifyBlobKzgProof` test, the batch one then takes ages, so we might want to run this outside of normal...
we read the config from remote already, so the gap is the value in the service