add auth

[felicio]

what

• SIWE

how

• https://gnosza.gitbook.io/sn-api/architecture/authentication
• https://gnosza.gitbook.io/sn-api/guides/sign-in-with-a-wallet-signature

why

• privacy

[felicio]

to be added possibly here https://www.figma.com/design/1XbZL2WrTG5DqJO8DovE0H/Website----status.network?node-id=2180-9564&t=gESYsaSxmQSRYgSn-4 ?

What other private details should be shown now?

If for now it's rather about showing the user that the action was completed/claimed, I'm not yet convinced it's worth the effort atm (running the additional server and handling client session https://1.x.wagmi.sh/examples/sign-in-with-ethereum). Even if it means that from user pov, the "onboarding karma" action might seem unclaimed or coming from unknown source (captcha or gitcoin).

Felicio

Yes, it would be there.

Well, we are running the server anyway and i've already implemented session tracking and encrypted cookies.
I'd just be adding new /register /login /logout /me routes, you register by signing a predetermined payload. We don't need to do nonce as SIWE, current unix timestamp is enough with timeout of 20s. (wasn't planning on following the standard tbh as we're centralized here and can allow ourselves to do it more efficiently)

I do agree that we can leave it for later if too much of a time waster for implementation on the frontend. But we must have authentication for accomplishing these steps, backend wouldn't be able to verify who did what captcha and for whom without it

Filip