Capture App does not upload the signed message to backend #778
Labels
bug
Something isn't working
fix/feature verified
The fix has been verified by QA
priority:critical
Critical priority
Milestone
Description
The message content signed in App (serialized
signedTargets
) is different from the string uploaded to DIA backend asmeta
field. Currently, the App never provide the correct signed message to backend in any way.In order to verify the signature using the information stored on the backend, the App must have a way to upload the signed message to backend for all assets created from the App.
Environment
Limitation
Because the generated key pair is destroyed when the App is deleted, if the user ever deletes the App even once, we have no way to remake signatures with the original key pair for the assets created before the user deletes the App. (It's meaningless anyway since the user also lost their wallet when deleting the App)
We could use the new key pair to generate a completely new signature though.
The text was updated successfully, but these errors were encountered: