RudraPay
OPATES - Offline Pre-Auth Tokenized Escrow System
Created on 30th December 2025
•
RudraPay
OPATES - Offline Pre-Auth Tokenized Escrow System
The problem RudraPay solves
🚀 The Problem RudraPay Solves
RudraPay fundamentally addresses the critical vulnerability of modern digital finance:
the absolute dependency on stable internet connectivity to complete transactions.
By leveraging Classic Bluetooth for peer-to-peer data transmission, it empowers users to send and receive payments seamlessly in environments where traditional banking apps and UPI gateways fail.
🌍 Works Anywhere
It enables financial exchanges in remote rural areas, underground transit systems, flights, or crowded events (like concerts) where network congestion renders mobile data useless.
⚡ Reliable Experience
It eliminates the frustration of “server unreachable” errors and infinite loading screens by processing transfers locally.
🛡️ Enhanced Safety
It reduces the necessity of carrying physical cash in off-grid locations, minimizing theft risk.
🔐 Technical Trust
Through cryptographic token locking and atomic transaction protocols, it ensures that users can trust the integrity of every offline transfer, effectively bridging the gap between the convenience of a digital wallet and the reliability of physical currency.
Challenges we ran into
🚧 Challenges I Ran Into
Building RudraPay in 48 hours presented critical technical challenges that nearly derailed our project.
The most significant hurdle was Bluetooth message fragmentation - when transferring large amounts of tokens (300+), JSON payloads exceeded packet size limits, causing messages to split across fragments and leading to decode failures. We overcame this by implementing a message reassembly buffer that accumulates incoming fragments and uses intelligent brace counting to detect when a complete JSON message has been received, allowing us to successfully handle transfers of 500+ tokens.
Another major challenge was preventing double-spending attacks where users could send the same tokens multiple times. We overcame this by implementing a token locking mechanism that exclusively locks tokens during transfers with transaction-specific IDs - when a transfer starts, tokens are immediately locked and unavailable for other transactions until the transfer completes or fails, ensuring atomic operations and preventing race conditions that could compromise transaction integrity.
Tracks Applied (1)