-
dapplet principles
-
Inspiration
Current web3 architecture has two major drawbacks:
- It breaks WYSIWYS principle because of immanent UX-vs-Security trade-off in Dapp development
- It lacks of support for web2 web.
for more details see in this post on magicians forum.
What it does
We introduce improved web3 architecture by moving whole web3 tx processing into trusted wallet environment for write operations. Dapps supply wallet with meta data instead of sending binary tx. It solves 1st problem mentioned above. For legacy site support we introduce dapplet control plugin, which incapsulates wallet connection and injects UI control into legacy site.
How we built it
Dapplet-extension is a standalone chrome extension. We have forked WalletConnect repos and have extended it by new functionality.
Challenges we ran into
Current version is a simplified PoC. Wallet Security is a hard thing. Some security-relevant aspects should be re-implemented and cleaned. Some parts must be splitted into different parts because they belongs to different security domains.
Accomplishments that we're proud of
Web3 workflows on the top of legacy sites are possible now.
What we learned
WalletConnect Chrome Extensions
What's next for Dapplets: new dapp architecture supporting legacy web
- Rework architecture under aspects of wallet security.
- Collect feedback from Wallet Devs and Users
- Get funded for further work on the project
Log in or sign up for Devpost to join the conversation.