Sign up to save your podcasts
Or
Share Konrad Kopp, Co-Founder of Rhinestone
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Konrad Kopp, Co-Founder of Rhinestone
My guest today is Konrad Kopp, co-founder of Rhinestone. Rhinestone is an exciting project that's researching and developing smart account modules atop the ERC-4337 Account Abstraction standard.
AA modules promise to allow smart contract account owners to safely add new functionality and permissions to their accounts, without having to upgrade to new smart contracts. The module pattern described in the draft ERC-6900: Modular Smart Contract Accounts and Plugins aims to create an ecosystem of interoperable modules to augment the various 4337 implementations that choose to support it.
On this episode, Konrad and I discuss the different approaches to account abstraction contract architecture, including Safe and the ERC-2535 Diamond standard. We dive into the details of ERC-6900, and discuss the compelling Rhinestone video demo, which shows how a user might activate and disable smart account modules like Passkey validation, dollar cost averaging, and recurring payments. We also cover the grant that Rhinestone recently received from the Ethereum Foundation's 4337 team to develop a Module Registry, a public goods venue where security audit firms and others can attest to the safety of specific modules.
Links
Chapters
(00:00:00) Intro
(00:02:00) Rhinestone starter at EthDenver
(00:03:54) What is Rhinestone?
(00:06:30) Authentication as a module
(00:08:14) Types of AA Modules: Validators, Executors, and Hooks
(00:15:25) Modular Accoints vs Hot/Cold Wallets
(00:16:10) Approaches to Modular AA
(00:16:45) 4337 implementation approaches: Diamond ERC-2535 vs Safe
(00:23:30) State of Bundlers
(00:25:15) State of AA Modular Accounts ecosystem
(00:27:25) Diamond ERC-2535 vs Safe, continued
(00:30:45) ERC-6900 Modules: Run anywhere & no vendor lock-in
(00:33:11) State of ERC-6900
(00:34:05) Will we converge on one 4337 implementation? Gas vs security
(00:35:30) What does ERC-6900 specify?
(00:36:10) Rhinestone & the Module Registry
(00:39:00) EF Grant
(00:40:00) Migrating AA to a new interface
(00:42:40) Modules terminology
(00:43:20) Modules Summary
(00:44:30) Reference modular wallet implementation
(00:48:10) ModuleKit for Module devs
(00:49:25) Singleton registry
(00:53:15) Cool Module ideas
(00:56:45) Recovery module
(00:58:06) Session Keys Permissions Modules
(01:01:00) WalletConnect?
(01:02:15) Farcaster Passkeys and largeBlob
(01:03:45) Is Rhinestone for devs or end-users?
(01:04:50) Wallet vs Account
(01:06:12) ERC-6492: Signature Validation for Predeploy Contracts and ERC-1271: Standard Signature Validation Method for Contracts
(01:09:27) Mutating AA predeploy
(01:11:27) Cross-chain Smart Accounts
(01:13:45) Standardizing module frontend
(01:17:19) Outro
View all episodes
By nnnnicholasMy guest today is Konrad Kopp, co-founder of Rhinestone. Rhinestone is an exciting project that's researching and developing smart account modules atop the ERC-4337 Account Abstraction standard.
AA modules promise to allow smart contract account owners to safely add new functionality and permissions to their accounts, without having to upgrade to new smart contracts. The module pattern described in the draft ERC-6900: Modular Smart Contract Accounts and Plugins aims to create an ecosystem of interoperable modules to augment the various 4337 implementations that choose to support it.
On this episode, Konrad and I discuss the different approaches to account abstraction contract architecture, including Safe and the ERC-2535 Diamond standard. We dive into the details of ERC-6900, and discuss the compelling Rhinestone video demo, which shows how a user might activate and disable smart account modules like Passkey validation, dollar cost averaging, and recurring payments. We also cover the grant that Rhinestone recently received from the Ethereum Foundation's 4337 team to develop a Module Registry, a public goods venue where security audit firms and others can attest to the safety of specific modules.
Links
Chapters
(00:00:00) Intro
(00:02:00) Rhinestone starter at EthDenver
(00:03:54) What is Rhinestone?
(00:06:30) Authentication as a module
(00:08:14) Types of AA Modules: Validators, Executors, and Hooks
(00:15:25) Modular Accoints vs Hot/Cold Wallets
(00:16:10) Approaches to Modular AA
(00:16:45) 4337 implementation approaches: Diamond ERC-2535 vs Safe
(00:23:30) State of Bundlers
(00:25:15) State of AA Modular Accounts ecosystem
(00:27:25) Diamond ERC-2535 vs Safe, continued
(00:30:45) ERC-6900 Modules: Run anywhere & no vendor lock-in
(00:33:11) State of ERC-6900
(00:34:05) Will we converge on one 4337 implementation? Gas vs security
(00:35:30) What does ERC-6900 specify?
(00:36:10) Rhinestone & the Module Registry
(00:39:00) EF Grant
(00:40:00) Migrating AA to a new interface
(00:42:40) Modules terminology
(00:43:20) Modules Summary
(00:44:30) Reference modular wallet implementation
(00:48:10) ModuleKit for Module devs
(00:49:25) Singleton registry
(00:53:15) Cool Module ideas
(00:56:45) Recovery module
(00:58:06) Session Keys Permissions Modules
(01:01:00) WalletConnect?
(01:02:15) Farcaster Passkeys and largeBlob
(01:03:45) Is Rhinestone for devs or end-users?
(01:04:50) Wallet vs Account
(01:06:12) ERC-6492: Signature Validation for Predeploy Contracts and ERC-1271: Standard Signature Validation Method for Contracts
(01:09:27) Mutating AA predeploy
(01:11:27) Cross-chain Smart Accounts
(01:13:45) Standardizing module frontend
(01:17:19) Outro