Glad you like it, thanks for watching :) Also, just updated the repository with the brand new released candide version: github.com/tomw1808/erc4337-candide feel free to check it out
Arent bundlers just centralized entities that introduce more privacy and MEV issues then?
3 หลายเดือนก่อน
Awesome video! The only issue here for me is about the signer. It would be nice to have a decentralized structure to perform social logins, whatever, and get private keys for generating a signer for an user... I am looking for several solutions here, but still didn't find any suitable at this moment. I would appreciate if you could help on this subject!
3 หลายเดือนก่อน
I mean, free solutions and that don't rely on centralized services.
Hey, thanks. I am not 100% sure what you mean by "decentralized solution to perform social logins" - like multi-signature onchain wallets (they can be already, safe wallet supports this by default), or some solution to generate a private key from a SSO via a service like Facebook login, Google login (we do to some degree for Morpher Wallet, its a public codebase, you can check it out yourself). But that would be centralized again, probably not what you want. The new Candide Onchain wallet also support passkeys, if that's what you're looking for. They were released after I made the video, so they're not mentioned in the video. Anyways, hope that helps.
3 หลายเดือนก่อน
@@TomsCourses Thanks for the quick reply! I would like to have a free (or cheapest) solution, and not centralized (meaning the system doesn't have a single point of failure), for generating private keys for signers (and managing them) under some kind of common authentication (social logins preferred)... About passkeys, I took I look already and I think is a good solution, however I think it's too advanced for the moment. It can be integrated but it's not the main solution.
This will probably be my first project with Foundry. It has been on my toDo list for a while. But since I really want to learn to use AA for my future apps. Any specific application for AA or could you say that all your future DApps will use it?
I think the answer is: it depends. It depends on your target audience. It depends on your project economies. Someone still has to pay for the transaction, so it very much depends if that can be profitable or, at least, be break even. Also, it depends what your users want, or maybe already have. If they have onchain wallets already. If you are ok letting your users use onchain wallet, or if the on-chain wallets are just a transport mechanism for signed messages... Also, there are no real good libraries for account abstraction, nothing compared to wagmi/viem, its all pretty homegrown at the moment.
![[LIVE] : ONE ลุมพินี 84 วันนี้!! คู่เอก "ก้องศึก vs เมืองไทย"](http://i.ytimg.com/vi/3kuzsAIDf1c/mqdefault.jpg)
Hey, super nice teaching! Great intro, very clear, nice voice and tone.
great work sir, i have been waiting for someone to talk about the same end-to-end development.
Love it. Excellent job, Thomas
Glad you like it, thanks for watching :) Also, just updated the repository with the brand new released candide version: github.com/tomw1808/erc4337-candide feel free to check it out
Arent bundlers just centralized entities that introduce more privacy and MEV issues then?
Awesome video! The only issue here for me is about the signer. It would be nice to have a decentralized structure to perform social logins, whatever, and get private keys for generating a signer for an user... I am looking for several solutions here, but still didn't find any suitable at this moment. I would appreciate if you could help on this subject!
I mean, free solutions and that don't rely on centralized services.
Hey, thanks. I am not 100% sure what you mean by "decentralized solution to perform social logins" - like multi-signature onchain wallets (they can be already, safe wallet supports this by default), or some solution to generate a private key from a SSO via a service like Facebook login, Google login (we do to some degree for Morpher Wallet, its a public codebase, you can check it out yourself). But that would be centralized again, probably not what you want. The new Candide Onchain wallet also support passkeys, if that's what you're looking for. They were released after I made the video, so they're not mentioned in the video. Anyways, hope that helps.
@@TomsCourses Thanks for the quick reply! I would like to have a free (or cheapest) solution, and not centralized (meaning the system doesn't have a single point of failure), for generating private keys for signers (and managing them) under some kind of common authentication (social logins preferred)...
About passkeys, I took I look already and I think is a good solution, however I think it's too advanced for the moment. It can be integrated but it's not the main solution.
Cool master!
This will probably be my first project with Foundry. It has been on my toDo list for a while. But since I really want to learn to use AA for my future apps. Any specific application for AA or could you say that all your future DApps will use it?
I think the answer is: it depends. It depends on your target audience. It depends on your project economies. Someone still has to pay for the transaction, so it very much depends if that can be profitable or, at least, be break even. Also, it depends what your users want, or maybe already have. If they have onchain wallets already. If you are ok letting your users use onchain wallet, or if the on-chain wallets are just a transport mechanism for signed messages... Also, there are no real good libraries for account abstraction, nothing compared to wagmi/viem, its all pretty homegrown at the moment.
10