Open alonmuroch opened 1 day ago
this is basically what commit boost does at its core ? https://commit-boost.github.io/commit-boost-client/architecture/overview we also have already integrated a custom domain #106
is anything else missing in your opinion?
Following the pre-conf notion (https://dear-twist-ac1.notion.site/Preconfirmations-API-Specification-1363b4619cb080a6a4cfd170c61771bc), all validators will need to perform a common step, which is signing a delegation.
I suspect future “validator-commitment” modules will also need such signatures.
My recommendation is to establish a generalized “sign arbitrary data” API between VC and commit-boost, with a dedicated domain type that renders slashing impossible. This will enable commit-boost modules to request the VC (and DVT clusters) to sign arbitrary data, specifically in the pre-conf scenario, a delegate message.
Pros:
Cons: