The problem WarpPay solves

Onchain users often have to jump between different tools just to send money, request payments, run airdrops or set up scheduled or recurring transfers, but what if you could have this in your social Farcaster and Coinbase feeds?

WarpPay brings it all together in one place

Send tokens or native coins across multiple EVM networks without worrying about hidden fees, in a really easy way. Use Farcaster usernames, ENS / Basenames or simply wallets seamlessly.

Create payment Request links that appear directly in Farcaster feed and Direct Casts (also supporting Coinbase feed, powered by Minikit) so anyone can pay you with couple clicks. Also can have a custom reason, explaining what is it for or threatening your cousin because he owes you... Up to you! It will show in the feed and also when they join!

Distribute tokens or coins to a lot of addresses in a single transaction using our Airdrop feature, it is easy to search friends or randomize your airdrops between your following and followers lists, everything in just few clicks!! but you also can use CSV or manual lists with (always) Farcaster names, ENS, Basenames and wallets support.

Schedule one-time or repeating payments ahead of time so you never miss a deadline.
This scheduler has an earn system where anyone can get 1% executing scheduled txs when the time arrives!
The automated system that detects new payments, sends notifications and automatically executes it after a period of time is under development and couldn't get finished on time, although all the onchain part is fully working.

Challenges I ran into

I leaned heavily on continuous user feedback to guide every iteration. Early on, I realized that a single, monolithic interface wouldn’t scale as features grew, so I refactored into a truly modular architecture: a core secured and public smart contract (linked on project links) powering the miniapp in a decentralized way.

Striking the balance between power and simplicity was another hurdle. With so many workflows: multi-chain utility feed integrated, Farcaster usernames, ENS names resolution, onchain scheduling, airdrops using Farcaster data follower/following lists, the UI risked becoming overwhelming. Thanks to real-world testing, I distilled complex flows into clear, contextual interactions and real-time previews, turning potential friction into moments of delight.

Finally, weaving all pieces together: RPC reliability, gas abstraction, name resolution, batch operations, decentralized schedules... took rigorous testing and changes and will take more to get perfection. Each obstacle taught me the importance of resilient design: graceful fallbacks, inline validation, and a relentless focus on “What would make this feel magical for the user? What would I need?” And that's what I am and will be always building.

The worst obstacle has been working alone, I am a team guy but circumstances are what they are, so I really appreciate everyone who tested, gave feedback or any kind of support.

There is a lot more to do but couldn't complete on time: better UX and UI, more customization of links and feed integration, a decentralized escrow system, and anything else people needs