-
Notifications
You must be signed in to change notification settings - Fork 407
Do not default to storing InMemoryChannelKeys
keys on disk
#1209
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
Comments
This is complicated by the fact that the |
Yea, I played with it a little bit and found that. It's further complicated by the fact that InMemoryChannelKeys' serialization is a public API and ideally we wouldn't break it by splitting the serialization logic half into KeysInterface's read method (otherwise you just break up the read code into parts). Not quite sure what the forward direction here is, but maybe it's just swapping around the deserialization stuff to do what we want and working on serialization later. |
Note that this is still an issue for now, but #1867 did the first step of ensuring we can read variants that don't store the keys. Now we just have to wait a few releases and then stop writing backwards-compatibility data. |
We can re-derive these on startup, so we should. Using
KeysInterface
's read method makes this easy, but we probably want to move the write method intoKeysInterface
as well (if practical) to make things symmetric.The text was updated successfully, but these errors were encountered: