-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arbitrary data signature API #195
Comments
this is basically what commit boost does at its core ? https://commit-boost.github.io/commit-boost-client/architecture/overview is anything else missing in your opinion? |
So just implement signer API for that? |
The API is already implemented for local keystores, and Web3 signer |
@alonmuroch let me know if anything missing or if we can close this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
The text was updated successfully, but these errors were encountered: