Skip to content
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

rought draft: BRING YOUR OWN DSM (for permissiones staking vaults) [very very WIP] #911

Draft
wants to merge 2 commits into
base: deposit-logistics-lib
Choose a base branch
from

Conversation

mymphe
Copy link
Contributor

@mymphe mymphe commented Dec 27, 2024

This PR includes a simple way to validate owner's validation of deposit data (Similary mechanism to DSM but with owner of the vault acting as the sole guardian)

Copy link
Member

@folkyatina folkyatina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ERC-1271 maybe?


bytes32 currentDepositRoot = _depositContract.get_deposit_root();
bytes32 securityMessageHash = keccak256(abi.encodePacked(GUARDIAN_SIGNATURE_PREFIX, currentDepositRoot, depositDataRoots));
address signer = ECDSA.recover(securityMessageHash, _guardianSignature.r, _guardianSignature.vs);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like it's worth to push this implementation a bit further over the abstraction path.

We can support ERC-1271 here and thus the other contract can be a guardian.
We can have an implementation of the "Lido Vaults DSM" as the guardian contract, so we can interchange them.
So, we can have some vaults protected by EOA guardian and some — by DSM committee.

WDYT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants