Big news: Cloakd is now integrated with @sideshiftai 🎉
Creators, promo sellers, and KOLs, can now accept any token on any chain, fully non-custodially, powered by SideShift’s swap engine.
If you accept crypto payments, try it here: https://t.co/koW9Ok8e7V
More coming soon👀
@akindo_io Super exited to pitch https://t.co/843KWk73aL 🔥
Making crypto payments Venmo-simple: no wallet sharing, multi-chain, non-custodial.
Good luck everyone!
@sideshiftai@akindo_io Big thanks to @sideshiftai for featuring Cloakd 🙌
Loved building on SideShift during the Akindo buildathon and looking forward to what’s next and getting Cloakd into more hands ♥️
The SideShift Buildathon with @akindo_io produced real products.
One of the standout projects: @AiCloakd - private payment links, cross-chain, no wallet address shared.
Built with the SideShift API. 🧵
@bitrusxbt Yeah this is the first reason I build https://t.co/e13UlOHG3N -> it will allow you to make crypto payment requests without sharing your wallet!
@fatimaa6594@zama Without shilling too much ;p I've build cloakd to create crypto payment request that you can share without exposing your public wallet address. What do you think?
@laron0791698056 @zama That's is why we allow you to create payment requests without sharing your wallet. Just a private payment link. Never share your wallet again :D
@frankNFT_eth@BitHide_io@beausecurity Curious: do you do a lot of on-chain transactions yourself? And what’s still the most stressful or annoying part for you? What makes it hard for you?
@asra2465@rainbowdotme Curious: do you do a lot of on-chain transactions yourself? And what’s still the most stressful or annoying part for you, even with a good wallet?
100%, different approaches, same root problem.
AI can help guide users before actions, and Cloakd focuses on the last mile: making sure the actual payment can’t go wrong (wrong chain, wrong address, wrong format).
Crypto needs multiple UX layers working together to really feel safe.
We can’t reverse this specific transaction unfortunately, no one really can once it’s on-chain.
What Cloakd helps with is preventing this before it happens: instead of sharing raw addresses + networks, you create a payment request with the correct chain locked in. The sender just pays, no dropdown mistakes.
If your friend ever sends/receives USDT across chains again, this removes that stress completely.