You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Staging Group
Group ID: 80355153990906273588811747340638
Production Group
Group ID: 65607750107025524717746661667760
So what is required is we use Bandada service for connecting the real eth address of the user , with their AA address comes from Thirdweb after login with email.
It might be 2 separate calls
one for adding the member before loading the first modal
second: for sending proof when the user clicks on connect in first modal.
then we show the success model.
No need for the integration replaced with the backend, the front end should not break the backend logic, we only want to say we're using Bandada
DOCS: https://api.bandada.pse.dev/
Staging Group
Group ID: 80355153990906273588811747340638
Production Group
Group ID: 65607750107025524717746661667760
So what is required is we use Bandada service for connecting the real eth address of the user , with their AA address comes from Thirdweb after login with email.
It might be 2 separate calls
No need for the integration replaced with the backend, the front end should not break the backend logic, we only want to say we're using Bandada
Sample code is here: https://github.com/GeneralMagicio/pairwise-rf4
Ask @mmahdigh for the API key.
The text was updated successfully, but these errors were encountered: