Smart Sessions🧠 - DCA Demo

I requested permissions dapp side in order to set up DCA strategy, and then disconnected from the dapp.

With the permissions, the dapp continued to execute the strategy in the background, without any further action from me!

This is how it works👇

Web Team Lead & Research Team Lead @reown

how is it different from ERC7579 which can support sessions?

Toolkits to build onchain UX → /reown. Builders of the WalletConnect Network. For the WalletConnect Network, please visit @walletconnect

Founder @payflow /payflow payflow.me /crimea 🇺🇦

7579 module should be implemented wallet-side. When wallets do it, dapps still need a way to communicate with them and ask for permissions, and spend permissions after that.
@reown SDK enables you to do all of that as it provides a nice abstraction layer.

Fun fact, the wallet in the demo is actually AppKit Embedded Wallet, and it’s using 7579 Sessions Module 👌

Correct! We’re also doing a bunch of stuff to support 7702 with WalletKit as well.

Also technically, the abstraction isn’t over 7579, it’s over 7715.

Instead of a dapp saying “You have to use 7579 module; otherwise, it won’t work,” it says something like “okay, I’m asking you for permissions, and you handle it however you want.”

Permissionless + safe + 7579 sessions module is one way.
Another way could be 7710, for example. 
Regardless of the possibilities, the 7715 is the common standard to ask and give permissions.

Also if you’re looking to implement smart account dapp side, you should really look into AppKit Embedded Wallet. 
You can always DM me for help 😉

Thanks for the explanation, makes sense to abstract ERC7570 even further.

I am currently experimenting with permissionless x rhinestone for safe wallets :)

I assume this abstraction you're building will work with EIP-7702 as well, right?