Sign and propose transactions from snap

[chiefbiiko]

Our main motivation to build a snap is to have a "portable" version of our existing dapp, portable in the sense that one can interact with our protocol right from the MetaMask extension (snap homepage) regardless of the browser’s current url.

Not being able to propose write transactions from within a snap makes this level of portability difficult/impossible and one needs to fallback to a companion dapp (what we wanted to get rid of actually).

In our concrete case, we can somewhat workaround this limitation by dispatching all write transactions via a relay service, with the caveat that the user would need to pre-approve a bulk amount for transfers run from our contract as part of the snap installation process (installation is initiated from a dapp and thus the process can propose the approve transaction).

Would such workaround pass the security requirements? What’s the rationale to not allow snaps to propose write transactions?

Many have run into this #2049 #2502 #2056 #2200 #2395 (seems like the # 1 gotcha), lifting this limitation sure would enable great new use cases.