SRI - Accept Eddsa signatures throughout the application

[biscuitdey]

Overview

Previously we accepted only Ecdsa signatures in the SRI because we used Metamask to login and Metamask used Ecdsa signatures. But Ecdsa signature verification inside circom zk circuits is very https://github.com/eea-oasis/baseline/pull/752 & the available alternatives are not widely used (causing issues with https://github.com/eea-oasis/baseline/pull/752#issuecomment-1733898957). Keeping these issues in mind, SRI team has decided to use Eddsa signatures.

Reference

PR #752

Tasks

• [ ] Generate Eddsa signatures on the client-side
• [ ] Add Eddsa sig verification in auth

[ognjenkurtic]

Currently blocked by https://github.com/eea-oasis/baseline/issues/765

[biscuitdey]

Approach used (as suggested by Andreas):

1. get pubkey_owner from accounts in MM through API
2. `message = keccack256(pubKey_owner)'
3. call the MM signing function API with the message as payload and the target account to use
4. API returns signature
5. Convert hex signature into Bigint number
6. That is the EdDSA privkey
7. Then generate the EdDSA pubkey from privkey using circom crypto library
8. Then use circom crypto library to create EdDSA signatures with privkey

[biscuitdey]

Completed.