Skip to content
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

Merged
merged 5 commits into from
Oct 2, 2024
Merged

Add XIP-31: Message History request system #65

merged 5 commits into from
Oct 2, 2024

Conversation

jhaaaa
Copy link
Contributor

@jhaaaa jhaaaa commented Jun 28, 2024

No description provided.

@jhaaaa jhaaaa requested a review from a team as a code owner June 28, 2024 00:51
@jhaaaa jhaaaa requested review from tuddman and removed request for a team June 28, 2024 00:51
@nplasterer nplasterer requested review from rygine and removed request for tuddman August 27, 2024 17:32
rygine and others added 3 commits September 9, 2024 18:00
Co-authored-by: J-Ha <5481259+jhaaaa@users.noreply.github.com>

### 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.
Copy link
Contributor

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

Copy link
Contributor

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`.
Copy link
Contributor

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?

@jhaaaa jhaaaa merged commit 38d3130 into main Oct 2, 2024
1 check passed
@jhaaaa jhaaaa deleted the add-xip-31 branch October 2, 2024 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants