Hello All the Magicians,
A long time ago I published a thread and a medium article
Dapplets: Rethinking Dapp Architecture for better adoption and security.
While we are mostly focused on the Dapplets project, we have decided to split-off the Wallet related part of it into the separate project S.O.W.A. - Secured Open Wallet Architecture.
Articles:
Part 1: Introducing S.O.W.A. – Secured Open Wallet Architecture
Part 2: Implementing S.O.W.A. – Secured Open Wallet Architecture
What is it about?
S.O.W.A. — is a general chain agnostic standard for scripts running in the Wallet’s sandbox and describing both the confirmation View and the Action execution plan.
What is the advantage?
- Interoperability between Wallets.
- WYSIWYS Views.
- Suitable for a wide range of hardware and security requirements.
- Modular and extensible architecture.
- Transaction batching (User confirms one Action starting many transactions).
- Allows gas payments for infrastructure providers like Wallets, Bridges and Relays
- Easy to audit; explicit specifications and audit status.
We have started work on S.O.W.A. because we need the standard for our Dapplets project and believe it would be useful for many other projects too.
Our work is still in progress, but we hope to start a discussion between Wallets and DApp developers to create new standards for better UX and interoperability.
Acknowledgements
A lot of thanks to @danfinlay, @JamesZaki and @ligi for their support and feedback!