Dshamir makes Mike quicker on its feet and safer with its keys
Three commits add caching for speed and a way to swap the master encryption secret without breaking anything already locked up.
Dshamir wired in Redis, an in-memory store that parks frequently-needed data so the app doesn't recompute or re-fetch it every time, plus standard browser caching instructions to cut repeat work. The payoff is a snappier system under load, though the routes that benefit still have to opt in.
The more interesting change is around stored secrets. Mike encrypts each user's saved API keys, and until now the secret that locked them could not be changed without orphaning every existing record. Dshamir's approach lets the team introduce a new secret while old data keeps decrypting under the old one, then quietly migrates as records are rewritten. The commentary flags that the key derivation here is a first pass, with a stronger method landing in later work.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?