14135
Tushar Soni
@tusharsoni.eth #14135
Building paywithglide.xyz. ex Robinhood, Uber, Apple
1466 Follower 491 Following
We have put in a lot of work to open up @paywithglide to *any* type of onchain transaction. You can enable cross-chain payments for simple transfers, swaps, deposit flows, contract calls, and pretty much anything you can think of.
Special thanks to @sinaver.eth for pushing us to support a wide variety of use cases.
https://warpcast.com/sinaver.eth/0xcbe7b881
Special thanks to @sinaver.eth for pushing us to support a wide variety of use cases.
https://warpcast.com/sinaver.eth/0xcbe7b881
I talk to founders who're looking to use @paywithglide in their dapp and decentralization is a topic we end up discussing often.
Thanks to the collaboration with amazing teams in the ecosystem, we're quickly making progress towards our decentralization goals.
https://warpcast.com/geralt/0xd5b6e729
Thanks to the collaboration with amazing teams in the ecosystem, we're quickly making progress towards our decentralization goals.
https://warpcast.com/geralt/0xd5b6e729
There's finally a growing discussion about moving away from PaaS into simple deployable fullstack services (thanks to @dhh of course).
I'm so here for it. We have been deploying our services to bare metal using https://kamal-deploy.org/ since day 1
I'm so here for it. We have been deploying our services to bare metal using https://kamal-deploy.org/ since day 1
Web2 companies pour so much money into perfecting checkout flows - A/B testing latency, clicks, UX, copy, colors for max conversion. So many payment options, that one is bound to work.
In Web3, it's more like "pay or leave"
Are you serious about your checkout flow? Then use paywithglide.xyz
In Web3, it's more like "pay or leave"
Are you serious about your checkout flow? Then use paywithglide.xyz
I have been gifted boosted casts by the farcaster overlords.
So, I must know -
So, I must know -
onchain payments are becoming the primary way to onboard crypto users to your product. @woj.eth added crypto payments for supercast in just a couple days, powered by @paywithglide
The execution on @base has been a masterclass since day 1. It is the primary force behind transforming Coinbase from a web2 product to a web3 native one.
Congrats @jessepollak, this promo is beyond well deserved 🥂
Congrats @jessepollak, this promo is beyond well deserved 🥂
There is an online-only hackathon organized by /framehack going on right now with a prize pool of $10,000!! Excited for @paywithglide to sponsor a small part for it
https://app.akindo.io/hackathons/vjOgv62Q4cZvVLg0R
https://app.akindo.io/hackathons/vjOgv62Q4cZvVLg0R
Fragmentation is a real problem. What's the solution?
I know we all love passkeys here, because it's 10x better ux than existing *crypto* ui.
But, it may not be 10x better than non-crypto apps, which is what we should be aiming for.
https://world.hey.com/dhh/passwords-have-problems-but-passkeys-have-more-95285df9
But, it may not be 10x better than non-crypto apps, which is what we should be aiming for.
https://world.hey.com/dhh/passwords-have-problems-but-passkeys-have-more-95285df9
We have been powering cross-chain payments in apps you love like @hypersub, @payflow, /herocast and more.
Now, you can instantly move tokens from one chain to another using our Instant Bridge!
https://bridge.paywithglide.xyz
Now, you can instantly move tokens from one chain to another using our Instant Bridge!
https://bridge.paywithglide.xyz
Another amazing demo by sinaver
Mint NFTs with Moxie (and other tokens!) using @payflow and @paywithglide
Mint NFTs with Moxie (and other tokens!) using @payflow and @paywithglide
I get that you want to send a random token to everyone but honestly, it's creating a mess. I have a hundred different tokens on 10 different chains.
Now, send whatever you want. The recipient will always get ETH on Base. Simple.
https://send.paywithglide.xyz
Now, send whatever you want. The recipient will always get ETH on Base. Simple.
https://send.paywithglide.xyz
We also wrote up a guide on how you can use @paywithglide to make your fiat payments work.
We give you a single wallet that can run transactions across 30(!!!!) chains and over a 100 tokens.
So all you have to do is take the fiat payment and execute the onchain tx.
https://docs.paywithglide.xyz/guides/pay-with-fiat
We give you a single wallet that can run transactions across 30(!!!!) chains and over a 100 tokens.
So all you have to do is take the fiat payment and execute the onchain tx.
https://docs.paywithglide.xyz/guides/pay-with-fiat
So, you're thinking of adding fiat payments to your dapp? Let's say you don't want to depend on too many third-party providers and want to build the solution in-house.
Here's how you'd do it 👇
Here's how you'd do it 👇
Update your dapps, folks — it's time to simplify the user journey by cutting out unnecessary clicks.
web2 companies put a lot of effort into optimizing the checkout flow and we need to do the same.
Watch how @myk removed several clicks from billsplit.xyz using @paywithglide
web2 companies put a lot of effort into optimizing the checkout flow and we need to do the same.
Watch how @myk removed several clicks from billsplit.xyz using @paywithglide
1. Make It Work
2. Make It Right
3. Make It Fast
4. Make it Cross-Chain
2. Make It Right
3. Make It Fast
4. Make it Cross-Chain
@myk did a livestream adding cross-chain payments to billsplit.xyz. He aimed to finish in 1 hour but took 30 minutes extra.
This week, we’re targeting a <1 hour integration time for @paywithglide
https://x.com/mykcryptodev/status/1827864082151784516
This week, we’re targeting a <1 hour integration time for @paywithglide
https://x.com/mykcryptodev/status/1827864082151784516
This is how p2p payments should work. web3 is filled with tokens and chains. Your preferred token is not your friend's preferred token. They may not even be on the same chain!
We're decoupling what you send from what your friend receives. DM me if you want this experience in your dapp.
We're decoupling what you send from what your friend receives. DM me if you want this experience in your dapp.
Love to see more activity on standardization of cross-chain calls. one of the drawbacks @wilsoncusack accurately calls out is "Reliance on privatized relayers". We're working hard to move everything onchain!
One big priority is to make things work across ecosystems as well. Think Solana <> Base transactions.
https://github.com/ethereum/RIPs/pull/31/files
One big priority is to make things work across ecosystems as well. Think Solana <> Base transactions.
https://github.com/ethereum/RIPs/pull/31/files
There are several consumer crypto apps that have an embedded wallet so they ask you to deposit a specific token on a specific chain.
Consumers - Do you prefer this? Or would you rather connect your existing wallet and pay from there.
Devs - why go for this experience?
Consumers - Do you prefer this? Or would you rather connect your existing wallet and pay from there.
Devs - why go for this experience?
Bought some grass
Before starting @paywithglide, one of the other ideas I was considering was tooling for merchants to accept USDC in their IRL stores.
The pitch for merchants was simple - no chargebacks & lower fees. Works great for small ticket stores where the processing fees can be upwards of 5%.
But, what's the incentive for the customer? You are essentially competing with their credit card and that's a tough one.
This is going to be a big challenge for acceptusdc.com, but I'm excited to see how they get around it.
The pitch for merchants was simple - no chargebacks & lower fees. Works great for small ticket stores where the processing fees can be upwards of 5%.
But, what's the incentive for the customer? You are essentially competing with their credit card and that's a tough one.
This is going to be a big challenge for acceptusdc.com, but I'm excited to see how they get around it.
With fragmented liquidity becoming a bigger issue with the launch of so many new chains, you would often need to bridge/swap your tokens across different ecosystems to do anything. That's no good.
The two main solutions I see are:
1. Unified Chain Balance
This solution provides you with a new wallet that consolidates your balance across multiple supported chains - giving you a "unified balance". The good thing is that you no longer need to worry about which tokens you hold when completing a transaction. However, you need to onboard onto a whole new thing to get this working.
2. Spend Your Existing Tokens Anywhere
In this approach, you continue using your existing wallet and tokens, possibly having a preferred token for spending, such as USDC. Dapps and wallets would then allow you to spend this preferred token regardless of what the transaction requires.
The two main solutions I see are:
1. Unified Chain Balance
This solution provides you with a new wallet that consolidates your balance across multiple supported chains - giving you a "unified balance". The good thing is that you no longer need to worry about which tokens you hold when completing a transaction. However, you need to onboard onto a whole new thing to get this working.
2. Spend Your Existing Tokens Anywhere
In this approach, you continue using your existing wallet and tokens, possibly having a preferred token for spending, such as USDC. Dapps and wallets would then allow you to spend this preferred token regardless of what the transaction requires.