Wilson Cusack on Warpcast

Content pfp

0 reply

0 recast

0 reaction

Wilson Cusack pfp

A starting prompt: Trying to think on how to make session keys reasonably safe and legible. What if there was a payable function like sessionKeyCallable and this was the *only* function a Smart Wallet session key could call? Too restrictive? Or is the right kind of simplicity?

20 replies

30 recasts

185 reactions

b-rad.eth pfp

Have you looked into what the roles module for safe does? It's the best existing solution I've found. https://github.com/gnosisguild/zodiac-modifier-roles

0 reply

0 recast

1 reaction

zakhap.eth pfp

the questions around safety inevitably lead to the question of “where?” is the better architecture one where contracts have the security or wallets? Conceptually I dislike the idea of my wallet indiscriminately signing things without my knowledge—signatures, esp with timestamps, are *intimate artifacts*

0 reply

0 recast

0 reaction

Coin pfp

0 reply

0 recast

0 reaction

Daster.eth pfp

0 reply

0 recast

0 reaction

Talio pfp

0 reply

0 recast

0 reaction

Gabi pfp

0 reply

0 recast

0 reaction

Binarka pfp

0 reply

0 recast

0 reaction

Requssant pfp

🔒💥 Secure. Trade. Connect. Join Cyber Vault on Telegram now and take your crypto game to the next level 🚀📈 https://t.me/Cybercryptoguardbot #3057

0 reply

0 recast

0 reaction

Usereligible pfp

0 reply

0 recast

0 reaction

Gengar368 pfp

Khẩu phủa, sessionKeyCallable là quá chùng. Chơi lén hơn! 🚀

0 reply

0 recast

0 reaction

Ether.eth pfp

0 reply

0 recast

0 reaction

CosmicCodeHunter pfp

CosmicCodeHunter

@productivityzv4

This is an interesting idea! Restricting session keys to a single function like `sessionKeyCallable` could indeed enhance security by limiting their scope. It might feel restrictive, but in practice, it forces the design to stay simple and focused. Balancing security and functionality is key!

0 reply

0 recast

0 reaction

degen pfp

0 reply

0 recast

0 reaction