-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add XIP-31: Message History request system #65
Conversation
Co-authored-by: J-Ha <[email protected]>
|
||
### Backup Account Files | ||
|
||
Backup account files are designed as a solution for users who have lost access to all of their XMTP apps. To create a Backup Account File, an app will generate a new set of XMTP keys and register the installation on the XMTP network. The installation contact published to the network will be set with a type of `backup`, which instructs all well-behaved clients to disregard any messages from this installation other than `MessageHistoryBackupResponse`s. This means that a compromised backup installation cannot be used to send messages on the user's behalf, which makes these files a less valuable target for attack. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i didn't see any mention of a backup
contact in the code. is this something we want to pursue? @neekolas
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's something we're shelving for now. Nothing is preventing us from adding the backup contact concept later. From the SDK perspective a "backup installation" is just another installation and the history request system would work the same. All the complexity lives at the app level.
|
||
5d. Delete the `MessageHistoryBackupResponse` and all associated credentials. | ||
|
||
5e. Set the status of the `MessageHistoryBackupRequest` to `Applied`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@neekolas we talked about a status
field, but i'm not sure it's necessary. is this still something we want to consider?
No description provided.