V2/V1 Removal

[nplasterer]

One time migration

In order to fully deprecate V2, we are going to need to do a one-time read of all your existing V2 conversations and dump them in to the libxmtp database.

One question we’ll need to answer as part of that process is whether we want to import messages where the other party has not yet setup a V3 identity. That would mean you would have messages in a conversation that are read-only, since there is no way to send new V3 messages to them. If the other party later sets up the V3 identity, we’d want some way for the message to become part of your V3 1:1 conversation with the user.

The advantage of doing it in advance of the other person migrating to V3 is that we can do the migration all at once and kill V2 earlier. The disadvantage is that we have to deal with these read-only convos, which can be complicated for devs. Maybe it’s not so bad because they’d be treated the same as a group that you were no longer a member of.

Need to think through the details here. When do we want to trigger this migration? Can we do it lazily?

• Period of read only
• Clear datadog metric tracking
• Import of all V2 messages into V3 database
  • Dedupe on message unique identifier