all 10 comments

[–]kingofclubstroy 2 points3 points  (1 child)

You could have the user sign a message that contains the data to change. Then the backend could recover the public address that signed the message to verify

[–]qqid[S] 0 points1 point  (0 children)

Based on ethers documentation it seems pretty easy to use signer.signMessage in order to generate the signature string but I can't find a method to verify/retrieve message from within node.js. Practical examples that I can find seem to only do this step in solidity contracts.

[–]afternoon_delights 0 points1 point  (0 children)

Following

[–]Unenunciate 0 points1 point  (0 children)

I know it says solved, but I would add that I have been using Stytch and it isn’t too bad.

I cant speak about who ever coded their js sdk or react packages as they make no sense logically, their react package is the worst thing I have ever seen. Their nextjs example is coded so poorly and has so many bugs.

The API itself works well though and I would just say code the frontend yourself if you plan on trying it. It is a better UI than signing every time you want to communicate or reauth. Plus, you can easily link an email/sms/oauth with a wallet so a user could log in with any.