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

Refactor(KeyManager): Don't persist master secret #322

Merged
merged 4 commits into from
Jan 2, 2023

Conversation

TheCharlatan
Copy link
Member

Derive account level keys on initialization.

This has the benefit of informationally segregating instantiated key manager.

Since the swap index is not mutable, every swap has to instantiate its own key manager. In order to informationally guarantee that each swap can only read and reach keys with its own swap index, derive the keys to the account index on key manager generation.

This is the last piece of the puzzle of the swap/wallet refactor that I discussed with @Lederstrumpf .

Derive account level keys on initialization.

This has the benefit of informationally segregating instantiated key
managers.

Since the swap index is not mutable, every swap has to instantiate its
own key manager. In order to informationally guarantee that each swap
can only read and reach keys with its own swap index, derive the keys to
the account index on key manager generation.
@TheCharlatan TheCharlatan changed the title Refactor(Keymanager): Don't persist master secret Refactor(KeyManager): Don't persist master secret Dec 30, 2022
@h4sh3d h4sh3d force-pushed the keymanagerRefactor branch 2 times, most recently from f428447 to 441b42a Compare January 2, 2023 11:47
Copy link
Member

@h4sh3d h4sh3d left a comment

Choose a reason for hiding this comment

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

tACK

@h4sh3d h4sh3d merged commit 5bcd15d into farcaster-project:main Jan 2, 2023
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