Mapping Out Status App, Keys, and Names


After today’s Multi-account discussion, I’ve started to revisit my older diagrams that attempted to map out how keys are derived and used within Status.

I have now attempted to create a map of Status and how keys will be derived and stored in the various parts of the “Status App.” This is also an attempt to get a logical overview of how we are sectioning off Status and how they interoperate with each other.

Hopefully we can use this as a diagram to make our arguments on what Status is and why we call various parts of it the things we do, and what we eventually want to agree on.

Here is a miro (previously called realtimeboard) link to what I currently have since that talk:


is it possible to share for status team? i can’t open it


updated the link, should work now