[feature request] Decouple signing from transaction creation about o1js

[mitschabaude]

Hey, thanks a lot for the feedback. This is on our testnet roadmap, the idea is that snarkyJS will only handle the transaction construction, and signing/sending is done by either another library or - preferably! - by interfacing with a browser wallet. We are in contact with the Auro wallet to make that work.

It's good to have it in its own github issue!

[mirceanis]

Excellent!

I'm developing a framework for verifiable data and decentralized identitiy (https://veramo.io) and would like to integrate snapps and some snarkyjs circuit logic.

This separation of concerns is very important, since these 2 aspects of transaction lifecycle don't always live in the same app, or even on the same machine.

An intermediate solution is to be able to serialize/deserialize signed transactions.
This way, the "signer" can act on a higher level and also build the transactions, not just sign blind data, but then the logic that sends transactions and waits for them can still live in a frontend.

Does this make sense?
I think serializing signed transactions is important for its own sake. I can create a different issue for that if you agree :)

[mitschabaude]

Makes sense to me!

Re: serializing transactions, to interact with browser extension we will have to send transactions with postMessage, and if that works then serialization is probably only a small step away. So I think it can stay coupled to this issue.

[mitschabaude]

This is done -- in current snarkyjs, you can leave out the fee payer key and sign with mina-signer