Ethereum Account Abstraction

Played around with session keys for the @base smart wallet over the weekend. 

Recommend checking out the docs in the smart-wallet-persmissions repo which does a good job at explaining each part of the setup.

Seems to  have a similar outcome to the modular accounts of 7579, and also have concepts like separate validation/execution stages that are compatible with 4337. Need to get a working 7579 example first to compare, but at first glance the new smart sessions from rhinestone/biconomy are a more complete solution - but the current smart-wallet-permissions is a v1 so is likely to change.

https://github.com/jamesmccomish/session-testing
https://github.com/coinbase/smart-wallet-permissions/tree/main/docs

I want to build a permissions module for the Zora Smart Account, which is a Coinbase Smart Wallet under the hood. Would anyone like to help me build this on a short term (1-4 week) contract — paid properly naturally.

Looking for someone for whom this is within reach.

I want to build a permissions module for the Zora Smart Account, which is a Coinbase Smart Wallet under the hood. Would anyone like to help me build this on a short term (1-4 week) contract — paid properly naturally.

Looking for someone for whom this is within reach.
https://warpcast.com/jamesmccomish.eth/0x5d781ab7

solidity & product & art. weekly crypto dev interviews @ web3galaxybrain.com. follow zora.co/nicholas

co founder of @metamask . Making computers behave for us.

Adding a 7579 module for each permission sounds as safe as trying to scoop electricity out of an outlet with a fork.

Meanwhile, allowances and method calling permissions are both trivial to write and already exist for the new metamask delegation toolkit. gator.metamask.io

I guess we gotta get the word to Zora..

Spend ETH (up to a limit defined by the user per tx) and call the mint fn. Nothing else.