Clarify `voluntary_exits` gossip topic after Capella
zilm13 opened this issue · 3 comments
I read the spec as topic is fixed to Capella after Capella:
https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md?plain=1#L121
While EIP-7044 is not clear on this.
Do we use current fork topic for gossip or Capella in Deneb and after?
I understand it's current fork for symmetry with all other topics
@dapplion we do the same but "due to the lock-in use of CAPELLA_FORK_VERSION" confuses me. At least would be good to confirm, that all clients are using Deneb fork id for exits gossip topic on Deneb.
We had few reports on no peers for this topic. I'd rephrase spec to "despite of" if we do the same job (changing topic for a new fork) as always.
yes as per lodestar impl, only the signature fork domain stays fixed while current topic is used