on the first rehydration this value could be undefined

Is it also true for other values from the keyserverInfo? Should we also handle them somehow?

Is the default_role column nullable at this point?

Use better error code

Rebase

Rebase

Move encrypting inside try-catch block

Do we use a similar approach in other reducers? Should we use the same approach there?

Rebase

Rebase

Are there some places where we're expecting only ThreadInfo and not MinimallyEncodedThreadInfo (or the other way around)? Is it possible to modify ThreadInfo type to be what it already is or MinimallyEncodedThreadInfo (type ThreadInfo = { ... } | MinimallyEncodedThreadInfo)? That might be a more maintainable and much simpler approach.