Fran Vañó on Warpcast

Daniel Lombraña pfp

Daniel Lombraña

One of the main pain points on web3 UX is handling your own wallets. While for most of us here, we are ok with it, the truth is that most people wont try to setup a hardware wallet or anything similar to be on the safe side. For this reason we've decided to create wallets for you, but with a different approach.

1 reply

0 recast

1 reaction

Daniel Lombraña pfp

Daniel Lombraña

While most of the solutions create a standard wallet, we do something different: we create for you a multi-sig. Why a multi-sig? Well, because we want you to be able to leave the nest whenever you want, and be 100% sure that you can trust us in the process.

1 reply

0 recast

1 reaction

Daniel Lombraña pfp

Daniel Lombraña

How's that possible? Well, because the wallet will have several owners, and when the user wants to leave and run its own wallet, all the user has to do is request it, and after some validation, the user will kick us out of the multi-sig. We believe this is the best approach for security and autonomy.

1 reply

0 recast

1 reaction

Daniel Lombraña pfp

Daniel Lombraña

You will not loose anything in the process, and as a user, you can trust the process as kicking us out of the multi-sig will be another operation within the txs of the wallets, ensuring that everything has been done properly and transparently.

1 reply

0 recast

1 reaction

Daniel Lombraña pfp

Daniel Lombraña

You can find more in this blog post written by @superxi https://blog.astaralabs.com/post/soft-ramp-web3-ux

1 reply

0 recast

1 reaction

Phil Cockfield pfp

↑ I see "DID" (Decentralised ID) mentioned by @superxi in the first paragraph, and immediately goes onto my "read carefully" reading list.

2 replies

0 recast

2 reactions

Fran Vañó pfp

IDK if you have already read it or if it is still on your reading list, but please let us know your thoughts. It is very important for us to know the Web3 community's opinion about our protocol.

1 reply

0 recast

1 reaction

Phil Cockfield pfp

Reading/digesting this weekend and will loop back to you Fran. 🧠🫀..🌳

1 reply

0 recast

2 reactions

Phil Cockfield pfp

(starting with caveats, I'm totally unqualified to hold a position on most everything...especially "Web3" whatever that actually means! I try to remain in "beginners mind" (n00b mind)...so all opinions come with large lashings of "salt," to be held lightly). In any event, this is super interesting! My read, is that what's being surfaced to the user within your system is somewhat akin to an "embedded wallet" (to borrow privy's term, say) - a lightweight, initial wallet, with minimal to no setup...BUT in your case, you're using a multi-sig design to provide the "hand holding" so as to keep this lightweight embedded wallet "minimum-viable-secure" before handing it off to full self0sovereignty? How was that for a poorly worded, basic stab at the gist of the idea? Am I on basically the right track? The idea of multi-sig here is super interesting. If I've got that idea right, the applications (more broadly than your initial example) are super rich. <NB: that prob doesn't help you much> - but thx for the read!

1 reply

0 recast

0 reaction

Fran Vañó pfp

First of all, thanks for reading the blog and sharing your thoughts/questions with us. We appreciate it. And yes, we use the multi-sig approach to allow the users to execute transactions (without paying any gas fee) and manage them by themselves when they feel comfortable with the technology. This way, the users will always own the generated assets during their experience in our app.

1 reply

0 recast

0 reaction

Daniel Lombraña pfp

Daniel Lombraña

Thanks a lot for the feedback @pjc Your schema is perfect, and I think we should use it from now on :D Because it shows what's going on behind the scences. Also, after reading your comment I was thinking that we can use the self-sovereignity approach in our explanations as this will help people, specially from the web3 community, to understand how we are building something different that takes care of users on the long run. We're desinging a solution that should work now and in the future, plus always showing full transparency about our approach. Moreover, we have built this solution as a headless solution so we will open it up for others to try it and play with it within their own products. Again, thanks a lot for all the feedback. Everything is welcome!

1 reply

0 recast

1 reaction