BridgePay

Demo

About

The problem it solves BridgePay solves one of the most fundamental issues. The cryptocurrency industry has reached a critical inflection point where companies operate across multiple blockchains by necessity, not choice. Today's crypto-native businesses find themselves trapped in an operational nightmare when it comes to something as fundamental as paying their employees. A typical company might have developers on Ethereum, marketing teams preferring Base for lower fees, and remote contractors comfortable with Arbitrum. This fragmentation forces companies into a weekly ritual of pain, manually switching between different wallets, calculating gas fees across networks, and executing dozens of separate transactions just to complete payroll. The human cost is staggering. Finance teams spend several hours every pay period juggling multiple interfaces, constantly switching between MetaMask networks, and praying they don't make a costly mistake when copying wallet addresses. One mistyped character can send thousands of dollars into the void. The operational overhead doesn't stop there, companies must maintain separate accounting for each chain, reconcile transactions across multiple block explorers, and manually track which employees have been paid on which networks. For airdrops and token distributions, the complexity multiplies exponentially. Projects attempting to distribute tokens to thousands of users across multiple chains face a logistical impossibility, often resorting to centralized exchanges or third-party services that charge hefty fees and compromise on decentralization.

How it's made

Challenges we ran into I didn't ran into a specific bug while building this project, but the process in itself was so intricate that the slightest of missteps can lead to dysfunction. Let's talk about deploying the contracts and creating a bridge between Ethereum Sepolia and Arbitrum Sepolia, I had to first deploy my contract on both Ethereum Sepolia and Arbitrum Sepolia, note down both the contract addresses, allowlist the destination chain selector on source contract, allowlist both the sender address and source chain selector on destination contract and repeat that for other chains as well. This manual process was so error-prone and tedious that we developed automated Foundry helper functions and Makefiles to orchestrate the entire cross-chain deployment process, transforming hours of mistake-prone work into reliable, repeatable deployments