Open mujabmuneeb opened 2 years ago
Creates Weba-wallet table inside dynamoDB.
Is this new code for a new table on the backend, separate from the user tables we already had?
https://github.com/webaverse/api-backend/blob/ee4618e2c2fffd5fbccb2eff7687ff9eb60f1f69/index.js#L473
Are all of the endpoints like discord going to be moved to this storage solution? What happens to all of the old accounts that already exist?
I think I somehow failed to communicate properly earlier, but it doesn't affect any user or any user's data it only deals with the User's local storage. For better understanding let me share the flow diagram.
Creates Weba-wallet table inside dynamoDB.
Is this new code for a new table on the backend, separate from the user tables we already had?
https://github.com/webaverse/api-backend/blob/ee4618e2c2fffd5fbccb2eff7687ff9eb60f1f69/index.js#L473
The backend part makes sense but this repo should not implement it, since I think it already exists.
Update:
Removed DB from wallet's backend and now using existing DB user's table to fetch and update his data. Temp key feature has been removed, replacing it with an encrypted mnemonic. Now, user data will be fetched/update via encrypted privateKey(mnemonic) we will receive from App.
Verifies postMessage(origin) from Webaverse app and return data as per request.
Creates Weba-wallet table inside dynamoDB. Contains three routes:
New temp token will be returned on login/ or on registration.
===================
On Webaverse App: (Ref: https://github.com/webaverse/app/pull/1762)