Change Details

Instead of JSON-serializing and deserializing social proof, we can store it directly as a map attribute in DDB. Depends on D11547

Instead of JSON-serializing and deserializing social proof, we can store it directly as a map attribute in DDB. NOTE: Note this is breaking change - previous users with String social proof in DDB will fail. I found only 3 wallet users on staging and none on prod. I prefer manually migrating (or deleting) these 3 rows instead of keeping this code backwards compatible Depends on D11547

Instead of JSON-serializing and deserializing social proof, we can store it directly as a map attribute in DDB. NOTE: Note this is breaking change - previous users with String social proof in DDB will fail. I found only 3 wallet users on staging and none on prod. I prefer manually migrating (or deleting) these 3 rows instead of keeping this code backwards compatible Depends on D11547