Conversation
| - Valid values: `1` to `4`. | ||
| - This field is set only when `is_aggregator: true`. | ||
| - Semantics: | ||
| - `1`: least proof efficiency, fastest proof construction. |
There was a problem hiding this comment.
I would suggest renaming "least/highest proof efficiency" by "biggest/lowest proof size".
|
lgtm! |
|
|
||
| - Dynamic committee assignment changes | ||
| - Changes to validator churn/activation logic | ||
| - Multi-message proof batching beyond one aggregate-per-message semantics |
There was a problem hiding this comment.
is this next devnet i.e. devnet-5? because right now proposer signature needs to be over whole BlockWithAttestation and not just proposer attestation
There was a problem hiding this comment.
I meant if we can aggregate proofs over different messages into one so that each block can have single proof, even with multiple messages. Currently leanVm supports recursive aggregation over a particular message, I'm guessing it's possible to aggregate proves over different messages into one but not sure if it is on the roadmap. Also, I'm unaware if we have had any discussions about devnet-5.
I think this is not binding in anyway so we can leave it here.
There was a problem hiding this comment.
yes this is not a devnet4 concern but devnet5 conversation
|
|
||
| ## Configurations | ||
|
|
||
| - `validator-config.yaml`: TBD |
There was a problem hiding this comment.
i don't see any configuration change in this for validator-config
4 participants
No description provided.