Not much information yet but creating an issue to avoid forgetting it.
Once ETH2 is deployed and EIP-4844 is deployed, we should start investigating how we could use the new data availability capabilities to verify offchain voting.
From what I understand with what is written there, we could create c data vote commitment with a KZG proof and from there get any information if needed.
I think a few questions there remain for example:
Do we want to use the Eth network directly for data availability ?
Is there a limtation there
Maybe see if we can create any other constraints on the data to avoid having issues. For example the data size ?
Not much information yet but creating an issue to avoid forgetting it.
Once ETH2 is deployed and EIP-4844 is deployed, we should start investigating how we could use the new data availability capabilities to verify offchain voting.
From what I understand with what is written there, we could create c data vote commitment with a KZG proof and from there get any information if needed.
I think a few questions there remain for example: