Thank you @raze-sag for your suggestion and detailed use case! We're happy to let you know that we’ve started working on implementing this feature to allow signing messages with a user’s private key directly through the Wallet API. This will help enable use cases like client-side encryption and cryptographic challenge solving. The feature will be available soon, and we’ll keep you updated on the progress.

Thanks again for your valuable feedback! 😊

Great to hear that you are already working on that.
I'd love to help you testing this feature if you already have an early implementation for that endpoint.

Thanks a lot, that's quick

Thanks for your report, @raze-sag !

If you believe that our product is of some value to the world and that we are doing a good job, would it be daring of me to ask you for a lousy little star in the repository? 😇

@alegomes of course, thanks for reminding!

Just a small follow up question @SuperBatata ,

I have just checked out the branch and built the corresponding images to test the signing feature. And as I understand it, the data flow for signing a message is as follows:

This works in a scenario in which I host a web application and Walt.id including the wallet.

Would it be possible to realize a data flow in which a QR code is generated like the /openid4vc/verify endpoint of the verifier, which the user scans, selects the corresponding key to sign the message?

I hope that that's some how understandable😅

Thank you for the follow-up question @raze-sag and for testing the signing feature! 😊

We appreciate your suggestion regarding a QR-code-based flow similar to the /openid4vc/verify endpoint. This is a great idea and a very interesting use case. While we won't be developing it right now, we’ve added it to our backlog for future consideration.

Thanks again for sharing your ideas and helping us improve—feedback like yours is invaluable! 🚀