I have been thinking how stupidly hard it is to download and have crypto wallets… specially for new people who are not from tech background.
So I vibe-coded a simple web-based crypto wallet that does exactly that…. Make a crypto wallet for you immediately when you visit the website. No bullshit.
Not sure if this is a million-dollar idea but I think it’s cool. And the tech stack is pretty simple too:
I am using Pimlico to make the EVM wallets, smart accounts using ERC7702, and Railway for backend for now. I used Cursor 2.0 and even after my $20 credit got over, they allowed me to use additional $35 worth of credits… pretty cool?
Would love your opinion on my project and tech stack
TempWallets.com
Things might break, but hey i think this is just an MVP and I’m just validating the vibe-coded idea instead of the whole app right now LOL
Do you guys think I should continue building on this idea? Or is it waste of time? If not this, then what?
Hi I actually work in Web3 and was in the engineering org for a well known L1. Your “solution” demonstrates that you do not have the faintest clue about Wallets. Please do not pursue this further. When your users lose their tokens, which they will, you will be responsible.
Also this exists, and is run by one of the largest payment processors in the world. You couldn’t even research your market properly https://www.privy.io/
This is harsh but thanks for sharing
First, you are wrong about Privy. Could you share the link to Privy’s solution similar to temporary wallets for end users?
There’s lot of emotions but nothing helpful. You don’t explain why will users lose their tokens? Perhaps if you point out, i might learn something new about wallets.
As someone who has had many crypto wallets and sold 1 BTC at $300 even I don’t remember how to get into some of my past wallets. Vibe coding things related to this topic is just going to make people pissed at you when they can’t access their wallets. If you are storing that information for them then you’re just 1 hack away from losing your customers money and they still will be pissed at you. If they are storing it locally they are just 1 phone upgrade or spring cleaning away from deleting their wallet credentials and being pissed at you for that exception to the rule. There is no version of this story where you could onboard users and convince them to deposit $100 and not end up pissed at you in under a year.
You should not vibecode apps that are dealing with money lol. Your are one NPM vulnerability away from getting sued to the ground.
Is this satire?
Cool idea, and I get the problem you’re trying to solve. Crypto onboarding is still way harder than it needs to be, especially for non-technical users. That said, anything involving wallets and real money gets complicated very fast. Once you’re generating wallets or touching transactions, you’re stepping into a world of security risks, legal gray areas, and potential liability, especially if someone loses funds or the tool ends up being used for something illegal.
I agree. But I also think all these problems are for future, and potentially solvable with money/investments. For now, my biggest question is: Can I find 1000 people who would use this every week? If yes then I have a PMF. Would you agree?
Because you're dealing with personal financial securitization and transactions on an international scale, I wouldn't touch this idea without having a firm grasp of the infrastructure and regulations. For example, you aren't necessarily responsible for the security a service you're using to provide the wallet, however, you are responsible for browser-based security as your application runs as a wrapper in the browser. One such thing is you need to make sure that attacks like XSS aren't going to immediately open up someone's crypto wallet. You need to make sure that you can utilize and properly store secure cookies, properly handle tokens, limit user access to one device, implement MFA etc. And you need to be able to do this without asking AI. Otherwise through irresponsible or negligent information handling you would be putting people's financial security and personal information at risk. Imagine telling a lawyer "but Claude said this software would handle data securely at the transport layer".
Or I can just put a “beta” next to the name, add Terms of Use and send a detailed email to the user once he signs up via Google SSO - essentially telling him to not put anything more than $100. This would solve the legal stuff for the most part.
Again, I agree to your concerns. But by this thinking, anything in the field of crypto is out of our scope of development. Thats not something I believe in.
You don’t seem to want to listen to the people here who know a hell of a lot more about this world, and everything ancillary to it, than you do.
Go ahead and do it, but don’t come crying to us when you’re living on the street due to a multi-million dollar judgment against you for negligence.
For funsies, I’m setting a one year reminder to check back and see how your bankruptcy proceedings went.
Good luck!
Is this bait? Is this entire post bait?
Considering that OPs URL is HTTP, it should be considered a malicious URL that if someone installs the software, like someone else said, their tokens would be stolen. Hence they avoided signifying the connection in their post. That or they plan to take advantage of anyone navigating to their webpage.
For the sake of the arguement they're simply ignorant, trying to offer a crypto wallet that isn't even hosted on a secure website, get out of here. Report this clown and their account.
No. This post is a waste of time. Your app is a waste of time.
Why?
Because you’re trying to scam people into giving you their wallet info. Go away.
You are high on some good stuff. There is no “giving” of anything in my prototype website. I don’t blame you for having this thinking, but you got the wrong dude, dude. And you can open it in a burner browser to see if I am lying and post screenshot if I am indeed a scammer. Or you go away, and stop spamming my posts!
What security measures have you considered? Web3 seems more difficult concerning security compared to traditional web development
Using industry-standard services like Pimlico to make secure wallets, and encrypting everything in db. I am quite sure there are ways to make it even more robust, but I think i should focus on knowing if there is a PMF for such a tool. Right?
And I am expecting 95% of users who will use this will be entry-level or just using it as temporary crypto wallet to get payments. I dont expect them to make this their life-savings account. After all, I am calling it TempWallets.
You have a crazy amount of liability you're taking on by offering wallets, and people who value security will not use it because they'd rather have a hardware wallet.
Not meaning to discourage you, but given that I get about a gazillion results if I google "free crypto wallet online", what exactly makes your app stand out?
That it does not require a learning curve. There are many crypto wallets, yes. But all of them require you to have a detailed on onboarding process like putting passwords and seedphrases.
Dont you think we need temporary crypto wallets like temporary emails?
But emails do not involve money. That's key difference.
Lmao on the user page it says that there are no settings available but you can turn on notifications to let you know that the settings are available but there are no settings to do so because again, they aren't implemented.....why would anyone trust their money on this website?
"we can fix it later"
Half the vibe coded API gateways I see lol.
6.5/10 ragebait
It's ass man
https://preview.redd.it/mpx40khkr37g1.jpeg?width=1320&format=pjpg&auto=webp&s=0084c705a8bf58eb52c031f50dd636787d5dbcaa
Don’t redeem the code, saar 🙏
Lmao
ngl i thought this was satire bravo
My friend no offence but this app looks like an app that is just there for a SCAM!
Maybe you would overhaul the design, right now this really just looks like some AI slop. Sorry mate!
Good luck with your idea.
Keep building, but tighten the problem you’re actually solving before chasing “million-dollar idea.”
Right now you nailed the “first wallet in 2 seconds” experience, which is great for demos, airdrops, or throwaway mints, but it’s probably not enough as a business. Figure out one sharp use case: e.g., creators dropping NFTs to normies, events issuing on-chain tickets, or apps that need burner wallets for trials. Go talk to 10–20 people in one of those buckets and see if they’d integrate TempWallets or pay for white-label flows, compliance help, or analytics.
I’d also think about how you’ll handle recovery, fraud, and abuse once traffic isn’t tiny. Services like Privy or Magic focus on smooth onboarding, while stuff like WalletConnect or even DreamFactory-style API gateways matter when third-party apps start calling you from everywhere.
Main point: keep going, but lock in a specific user and use case before you overbuild anything.
What are you talking about? Crypto wallets are extremely easy to download, create, and use?
Everyone has had or has ideas about being a "mi," I'd even say about being a "bi." But seniority shows that it's not quite like that. Do it for yourself and your personal knowledge.
Your idea: (theoretically) nice.
Your skillet: not existent.
My recommendation: make a to-do list app, make a weather app, get a proper computer science education and then revisit your idea after consulting a legal assessment.
Good luck!
Skillet… chuckles
Ayo, you don't bring your dev skillet everywhere? 😂 Damn autocorrect