{"username":"kurtlarsen","fid":4918,"attestations":["kurtlarsen.eth"],"displayName":"Kurt","bio":"Co-Founder @rhinestone ","pfp":"https://imagedelivery.net/BXluQx4ige9GuW0Ia56BHw/ddf47193-2cd4-4750-4727-507ab9a89200/original","primaryAddress":"0xdfe3bf3ded8f71bdd8674d39f9a0430aee4ed2a4","casts":[{"hash":"0x152bd6d185542aeb0fae45a2a16c1edf2de60008","text":"Yep, there are modules that exist in the ERC-7579 (modular smart account standard) ecosystem that can perform these functions. \n\nFor (1) you will need an offchain service that watches for new token events on the wallet. But is trustless. \n\n(2) is easy byproduct of solving (1)\n\n(3) I don’t think is possible. You could use something similar to (1) to auto burn","timestamp":"2025-08-14T21:47:12.000Z","url":"https://forkcaster.xyz/kurtlarsen/0x152bd6d185542aeb0fae45a2a16c1edf2de60008"},{"hash":"0x1d45e7af389e4e202633ae6cf9efd5ceff1e9603","text":"This was meant to be a quote post. Seems you can’t quote post into a channel. Initial post below \n\nhttps://warpcast.com/v/0x0ceba636","timestamp":"2025-02-13T08:11:52.000Z","url":"https://forkcaster.xyz/kurtlarsen/0x1d45e7af389e4e202633ae6cf9efd5ceff1e9603"},{"hash":"0x8c20b88188427a46e2c912253519664d78681882","text":"This is an interesting perspective. \n\nI don’t think it needs to be an either or. \n\nThe benefit of supporting EOA + 7702 is increased TAM for the developer.\n\nHowever, I would argue that there is no upside to giving new users an EOA + 7702, only downsides due to feature limitations and security. \n\nMy recommendation would be to support a smart account that is 7702 compatible. Upgrade the existing EOA users and give the new users a full smart account.","timestamp":"2025-02-12T20:50:49.000Z","url":"https://forkcaster.xyz/kurtlarsen/0x8c20b88188427a46e2c912253519664d78681882"},{"hash":"0x445a710a53bb915e5dd2104735067904af1b4a71","text":"Yesterday, we announced the Resource Lock Hook for ERC-7579 smart accounts.\n\nThis Hook Module enables any specialized execution layer to seamlessly integrate with ERC7579 accounts and execute any intent through a single signature.\n\nLaunching Q1 2025, with more to come!\n\nhttps://x.com/rhinestonewtf/status/1869044965797773656","timestamp":"2024-12-18T16:49:44.000Z","url":"https://forkcaster.xyz/kurtlarsen/0x445a710a53bb915e5dd2104735067904af1b4a71"},{"hash":"0xe0c0416285951773628216ce5afe4ec32261b4b0","text":"Thanks for hosting @reown @walletconnect \n\nThe notion of the account-centric developer platform is only just starting to take off. ERC-7579 is the shared standard that will bring this to fruition. Rhinestone is a vehicle to accelerate it","timestamp":"2024-11-11T11:25:13.000Z","url":"https://forkcaster.xyz/kurtlarsen/0xe0c0416285951773628216ce5afe4ec32261b4b0"},{"hash":"0xa1c8577c74c8dda3e6ec62699f57276911d147eb","text":"Onchain permissions for EOAs using Smart Sessions and EIP-7702","timestamp":"2024-10-30T22:09:39.000Z","url":"https://forkcaster.xyz/kurtlarsen/0xa1c8577c74c8dda3e6ec62699f57276911d147eb"},{"hash":"0x156f8961b55c2f30700e9e0c0de8441e7a5b2b97","text":"Introducing Rhinestone Protocol 1.0 🧩\n\nThe first smart account interoperability protocol\n\nTransforming smart accounts into the next open platform, aggregating and unifying the account stack to maximize distribution for devs.\n\nThe foundations for the account-centric dev platform 🚀\n\nFor the full write up: https://blog.rhinestone.wtf/rhinestone-protocol-1-0-hits-mainnet-695469dce425\n\nFor the summary: https://x.com/rhinestonewtf/status/1851277911363633506","timestamp":"2024-10-29T20:32:37.000Z","url":"https://forkcaster.xyz/kurtlarsen/0x156f8961b55c2f30700e9e0c0de8441e7a5b2b97"},{"hash":"0x317a85a89a09e49077d54e8fe1444462dc56cfb1","text":"Disaster planning for your self-sovereign users? \n\nYou need Social Recovery or the infamous Deadman Switch\n\nBoth Smart Account features are part of our open-source Core Modules. Available to anyone and everyone building on Modular Smart Accounts. \n\nCheck out our the guides ↓\n\nSocial Recovery https://docs.rhinestone.wtf/module-sdk/using-modules/social-recovery\n\nDeadman Switch https://docs.rhinestone.wtf/module-sdk/using-modules/deadman-switch","timestamp":"2024-10-28T18:43:00.000Z","url":"https://forkcaster.xyz/kurtlarsen/0x317a85a89a09e49077d54e8fe1444462dc56cfb1"},{"hash":"0xd89b94a922106d0e90d382370e1c9f519edbb681","text":"Hey Varun, \n\nWe've done a lot of thinking about this at @<unknown> and it's formed the basis for a lot of the open source work we've done with Safe, zkSync, Biconomy, ZeroDev, OKX, and a number of others. \n\nThe standard is called ERC-7579. This is a minimal standard for modular smart accounts. Modules are self-contained smart contracts that extend the functionality of a Smart Account. This will allow you to continue to support existing features (passkeys, gas abstraction, secure recovery mechanisms etc) but also provide new tools for the problems you raise.\n\n1. If a user wants to change apps they can import the account and enable a new signer dedicated to that app or enable a session key to give the app scoped access. \n\n2. No direct solution, but scoped executor modules and session keys can make this secure, whilst still open and programmable for applications.\n\n3. Any developer can build a module, which under the right permissioning framework, can allow apps/users to extend the functionality of their account","timestamp":"2024-10-15T19:47:57.000Z","url":"https://forkcaster.xyz/kurtlarsen/0xd89b94a922106d0e90d382370e1c9f519edbb681"},{"hash":"0x928c0634018aa71246b94b23afa1f879ee393955","text":"ERC-7579. \n\n35 modules, and we haven't even started! A slosh of compatible smart accounts inbound.\n\nerc7579.com/modules","timestamp":"2024-06-14T12:03:31.000Z","url":"https://forkcaster.xyz/kurtlarsen/0x928c0634018aa71246b94b23afa1f879ee393955"}],"note":"account hasn't signed the social smart contract; the profile is read-only on farcaster.xyz","farcaster":"https://farcaster.xyz/kurtlarsen"}