The problem BitSend solves

Payments have one fatal flaw – they require the internet.

There are 2.2 billion people without access to the internet. In
conflict zones like Iran, the entire network goes dark overnight. 185
million transactions were lost overnight. People cannot pay for
their food. Not because they cannot afford it, but because they
cannot access the network.

Each app has the same problem. No internet, no payment.

BitSend solves the problem

A hybrid offline crypto payment app. No internet required.

• Load funds online → stored as secure offline token
• Send via Hotspot , QR code and Bluetooth
• Settles on-chain via BitGo when the internet is available
• Built on Base: fast, cheap, ethereum-grade security
• Send to ENS names, rather than long wallet addresses
• Tamper-proof PDF receipts stored via Fileverse

Our Backed Wallet ensures double-spending is impossible.

Money that works when nothing else does.

Challenges we ran into

The core challenge

The biggest challenge wasn't making the single transaction work; the
challenge was making the entire offline payment process dependably work.

Not only do we need to coordinate wallet state, chain selection, transport
mode, and offline behavior, we need to do this simultaneously. This was
actually causing real issues in the early days: the UI would incorrectly
indicate readiness, the wallet might appear funded and ready for handoff
but not really be ready for handoff, or the transaction might fail
silently after the user changed networks or transport modes.

I made significant architectural changes to address these issues: I
centralized logic around clear state boundaries, splitting "prepare
while online" from "sign and hand off offline", and ensuring the UI
clearly presents the user with the status and recovery options rather than
allowing them to proceed in an invalid state.